You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2020/04/30 04:52:27 UTC

[GitHub] [druid] gianm edited a comment on issue #9791: Introduce extensibility support for Datasources

gianm edited a comment on issue #9791:
URL: https://github.com/apache/druid/issues/9791#issuecomment-621611255


   Is the idea that MultiDataSource would be something that exists and runs on the Broker, or on Historicals, or both?
   
   This seems sort of similar to the `SegmentWrangler` interface, which is used by the Broker in LocalQuerySegmentWalker to do direct queries over inline and lookup datasources. I wonder if these can be combined? What do you think?
   
   If not, then I wonder if this thing you're trying to do could be done in a style similar to SegmentWrangler? (Check out its SegmentWranglerModule, etc.)
   
   Are there use cases you have in mind other than redesigning UnionDataSource?


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