influxdb/services
Jonathan A. Sternberg 733d842812 Turn the ExecutionContext into a context.Context
Along with modifying ExecutionContext to be a context and have the
TaskManager return the context itself, this also creates a Monitor
interface and exposes the Monitor through the Context. This way, we can
access the monitor from within the query.Select method and keep all of
the limits inside of the query package instead of leaking them into the
statement executor.

An eventual goal is to remove the InterruptCh from the IteratorOptions
and use the Context instead, but for now, we'll just assign the done
channel from the Context to the IteratorOptions so at least they refer
to the same channel.
2018-03-08 14:03:20 -06:00
..
collectd Generate trace logs for a number of significant influx operations 2018-02-21 15:08:49 -07:00
continuous_querier Turn the ExecutionContext into a context.Context 2018-03-08 14:03:20 -06:00
graphite Generate trace logs for a number of significant influx operations 2018-02-21 15:08:49 -07:00
httpd Turn the ExecutionContext into a context.Context 2018-03-08 14:03:20 -06:00
meta Generate trace logs for a number of significant influx operations 2018-02-21 15:08:49 -07:00
opentsdb Generate trace logs for a number of significant influx operations 2018-02-21 15:08:49 -07:00
precreator Update logging calls to take advantage of structured logging 2018-02-20 10:04:19 -06:00
retention use underscore vs period, fix doc comment, add database name to CQ 2018-02-26 10:08:43 -07:00
snapshotter Update logging calls to take advantage of structured logging 2018-02-20 10:04:19 -06:00
storage series keys are produced in ascending order 2018-02-22 13:08:36 -07:00
subscriber Generate trace logs for a number of significant influx operations 2018-02-21 15:08:49 -07:00
udp Generate trace logs for a number of significant influx operations 2018-02-21 15:08:49 -07:00