justinborromeo commented on a change in pull request #7133: 6088 - Time Ordering On Scans URL: https://github.com/apache/incubator-druid/pull/7133#discussion_r263646652
########## File path: docs/content/querying/scan-query.md ########## @@ -194,3 +194,11 @@ Legacy mode can be triggered either by passing `"legacy" : true` in your query J `druid.query.scan.legacy = true` on your Druid processes. If you were previously using the scan-query contrib extension, the best way to migrate is to activate legacy mode during a rolling upgrade, then switch it off after the upgrade is complete. + +## Configuration Properties + +|property|description|values|default| +|--------|-----------|------|-------| +|druid.query.scan.maxRowsQueuedForTimeOrdering|The maximum number of rows returned when time ordering is used|An integer in [0, 2147483647]|100000| Review comment: I don't think that would work because priority queues can't have greater than INTEGER.MAX elements (the backing array is indexed with an int). ---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
