mirror of https://github.com/apache/druid.git
1f052b43c5
Druid currently has 2 serverViews, regular serverView and filtered serverView. The regular serverView is used to monitor all segment announcements from all data nodes (historicals, tasks, indexers). The filtered serverView is used when you want to watch segment announcements from particular tiers. Since these server views keep track of different sets of druidServers and segments in memory, they should be maintained separately. However, they currently share the same name for their executorService, which can cause confusion and make debugging harder especially in the broker since it is using both serverViews, the filtered view for normal query processing and the regular view to serve the servers table (I'm unsure whether this is intended or whether this is a good behavior). This PR changes it to a more obvious name. This PR also removes SingleServerInventoryView. This view was deprecated a long time ago and has not been documented at least since 0.13 (#6127). I also don't think this can be better in any case than BatchServerInventoryView. Finally, I merged AbstractCuratorServerInventoryView and BatchServerInventoryView as we no longer need AbstractCuratorServerInventoryView after SingleServerInventoryView is removed. |
||
|---|---|---|
| .. | ||
| aliyun-oss-extensions | ||
| ambari-metrics-emitter | ||
| cassandra-storage | ||
| cloudfiles-extensions | ||
| distinctcount | ||
| dropwizard-emitter | ||
| gce-extensions | ||
| graphite-emitter | ||
| influx-extensions | ||
| influxdb-emitter | ||
| kafka-emitter | ||
| materialized-view-maintenance | ||
| materialized-view-selection | ||
| momentsketch | ||
| moving-average-query | ||
| opentsdb-emitter | ||
| prometheus-emitter | ||
| redis-cache | ||
| sqlserver-metadata-storage | ||
| statsd-emitter | ||
| tdigestsketch | ||
| thrift-extensions | ||
| time-min-max | ||
| virtual-columns | ||
| README.md | ||
README.md
Community Extensions
Please contribute all community extensions in this directory and include a doc of how your extension can be used under docs/development/extensions-contrib/.
Please note that community extensions are maintained by their original contributors and are not packaged with the core Druid distribution. If you'd like to take on maintenance for a community extension, please post on dev@druid.apache.org to let us know!