[incubator-druid] branch 0.14.0-incubating updated: add note on consistency of results for sys.segments queries (#7034) (#7101)

[fj...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

fjy pushed a commit to branch 0.14.0-incubating
in repository https://gitbox.apache.org/repos/asf/incubator-druid.git


The following commit(s) were added to refs/heads/0.14.0-incubating by this push:
     new 9990e04  add note on consistency of results for sys.segments queries (#7034) (#7101)
9990e04 is described below

commit 9990e043896eb8023c1a98c7d3cdc957d93ec0ef
Author: Surekha <su...@imply.io>
AuthorDate: Tue Feb 19 21:09:10 2019 -0800

    add note on consistency of results for sys.segments queries (#7034) (#7101)
    
    * add doc
    
    * change docs
    
    * PR comments
    
    * few more changes
---
 docs/content/querying/sql.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/content/querying/sql.md b/docs/content/querying/sql.md
index 3f27491..883904c 100644
--- a/docs/content/querying/sql.md
+++ b/docs/content/querying/sql.md
@@ -571,6 +571,8 @@ The "sys" schema provides visibility into Druid segments, servers and tasks.
 ### SEGMENTS table
 Segments table provides details on all Druid segments, whether they are published yet or not.
 
+#### CAVEAT
+Note that a segment can be served by more than one stream ingestion tasks or Historical processes, in that case it would have multiple replicas. These replicas are weakly consistent with each other when served by multiple ingestion tasks, until a segment is eventually served by a Historical, at that point the segment is immutable. Broker prefers to query a segment from Historical over an ingestion task. But if a segment has multiple realtime replicas, for eg. kafka index tasks, and one t [...]
 
 |Column|Notes|
 |------|-----|


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org