gianm commented on issue #6088: Scan query: time-ordering
URL:
https://github.com/apache/incubator-druid/issues/6088#issuecomment-459570009
In that case what do you mean by `threshold`? The max threshold possible for
time ordering (which I guess should be a config)? Possibly return an
gianm commented on issue #6088: Scan query: time-ordering
URL:
https://github.com/apache/incubator-druid/issues/6088#issuecomment-459556301
I think it's fine to not add the feature to legacy mode.
This is an automated
gianm commented on issue #6088: Scan query: time-ordering
URL:
https://github.com/apache/incubator-druid/issues/6088#issuecomment-459191720
Ah, that's a good point. I can't think of a better kind of alternative. I do
think (1) would make the most sense, with as small a change as possible,
gianm commented on issue #6088: Scan query: time-ordering
URL:
https://github.com/apache/incubator-druid/issues/6088#issuecomment-458824423
IMO it’s appropriate and would just need to involve changes to the docs to
reflect new behaviors. Scan in that case would be able to start returning
gianm commented on issue #6088: Scan query: time-ordering
URL:
https://github.com/apache/incubator-druid/issues/6088#issuecomment-458616539
> @gianm How would this look from an interface point of view? Would we be
adding a new JSON field or is there an existing field where a user could
gianm commented on issue #6088: Scan query: time-ordering
URL:
https://github.com/apache/incubator-druid/issues/6088#issuecomment-414174269
> FYI: I'd just like to see this kept as option in the query, so ones that
do no need sorting avoid the performance hit.
Agreed, we should
