justinborromeo edited a comment on issue #6088: Scan query: time-ordering URL: https://github.com/apache/incubator-druid/issues/6088#issuecomment-459170520 The current output of the scan query is a collection of ScanResultValue objects (String segmentId, List<String> columns, Object events) where each ScanResultValue contains the rows from a specific segment. Time-ordering scan results will cause events to not be nicely grouped by segment...for that reason, I don't think it makes sense to use that format. The 3 options I've thought of: 1) Having a separate output format for time-ordered scans -> An example of such a format would be a collection of events where segmentId is a field of each event. 2) Returning a ScanResultValue for each event -> This is pretty bad because there would be a ridiculous amount of extra overhead from the list of columns. 3) Changing the output format for _all_ Scan queries -> I think this is a no-go because it would be a breaking change for existing clients Are there any better alternatives?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@druid.apache.org For additional commands, e-mail: commits-h...@druid.apache.org
