[GitHub] justinborromeo edited a comment on issue #6088: Scan query: time-ordering

2019-01-30 Thread GitBox
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 columns, Object events) where

[GitHub] justinborromeo edited a comment on issue #6088: Scan query: time-ordering

2019-01-30 Thread GitBox
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 columns, Object events) where

[GitHub] justinborromeo edited a comment on issue #6088: Scan query: time-ordering

2019-01-30 Thread GitBox
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 columns, Object events) where

[GitHub] justinborromeo edited a comment on issue #6088: Scan query: time-ordering

2019-01-30 Thread GitBox
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 columns, Object events) where

[GitHub] justinborromeo edited a comment on issue #6088: Scan query: time-ordering

2019-01-29 Thread GitBox
justinborromeo edited a comment on issue #6088: Scan query: time-ordering URL: https://github.com/apache/incubator-druid/issues/6088#issuecomment-458773614 The way Scan is written now, the "scan query doesn't retain all rows in memory before rows can be returned to client"

[GitHub] justinborromeo edited a comment on issue #6088: Scan query: time-ordering

2019-01-29 Thread GitBox
justinborromeo edited a comment on issue #6088: Scan query: time-ordering URL: https://github.com/apache/incubator-druid/issues/6088#issuecomment-458773614 The way Scan is written now, the "scan query doesn't retain all rows in memory before rows can be returned to client"

[GitHub] justinborromeo edited a comment on issue #6088: Scan query: time-ordering

2019-01-29 Thread GitBox
justinborromeo edited a comment on issue #6088: Scan query: time-ordering URL: https://github.com/apache/incubator-druid/issues/6088#issuecomment-458658358 Would it make sense to have both `timeOrder` _and_ the `descending` parameter (from BaseQuery)?