[GitHub] [druid] abhishekagarwal87 opened a new issue #10444: Better handling of different servers having different versions of broadcast table segments

[GitBox <gi...@apache.org>]

abhishekagarwal87 opened a new issue #10444:
URL: https://github.com/apache/druid/issues/10444


   ### Description
   Broadcast data sources can potentially have different segment versions on different servers. It can result in some inconsistencies
     - If a query involving broadcast data source is evaluated on different servers (such as join), the end result might be incorrect since different servers could have different versions of data. 
     - Broker may cache the result of join queries on its end. During the query execution, historicals may have an older version of data. However, once the broker caches it, the historicals will not be re-queried even if they update their data with a newer version of data. Thus, brokers will be left with stale query results.  The scenario is described here - https://github.com/apache/druid/pull/10366/files#r494684538
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



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