kfaraz commented on a change in pull request #11732:
URL: https://github.com/apache/druid/pull/11732#discussion_r733430393
##########
File path: docs/configuration/index.md
##########
@@ -1795,6 +1795,7 @@ See [cache configuration](#cache-configuration) for how
to configure cache setti
|`druid.serverview.type`|batch or http|Segment discovery method to use. "http"
enables discovering segments using HTTP instead of zookeeper.|batch|
|`druid.broker.segment.watchedTiers`|List of strings|Broker watches the
segment announcements from processes serving segments to build cache of which
process is serving which segments, this configuration allows to only consider
segments being served from a whitelist of tiers. By default, Broker would
consider all tiers. This can be used to partition your dataSources in specific
Historical tiers and configure brokers in partitions so that they are only
queryable for specific dataSources.|none|
|`druid.broker.segment.watchedDataSources`|List of strings|Broker watches the
segment announcements from processes serving segments to build cache of which
process is serving which segments, this configuration allows to only consider
segments being served from a whitelist of dataSources. By default, Broker would
consider all datasources. This can be used to configure brokers in partitions
so that they are only queryable for specific dataSources.|none|
+|`druid.broker.segment.watchRealtimeNodes`|Boolean|Broker watches segment
announcements from processes serving segments to build cache of which process
is serving which segments. This configuration allows the exclusion of segments
being served by realtime processes. By default, Broker would consider both
realtime and historical processes. This can be used to configure brokers in
partitions so that they are only queryable for Historical tiers or both
Historical tiers and realtime processes.|true|
Review comment:
Thanks for the review @techdocsmith , I have committed your suggestion.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
