[
https://issues.apache.org/jira/browse/DRILL-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Westin resolved DRILL-5462.
---------------------------------
Resolution: Invalid
> Drill needs a per-query option to force a sort for non-covering indexed
> queries
> -------------------------------------------------------------------------------
>
> Key: DRILL-5462
> URL: https://issues.apache.org/jira/browse/DRILL-5462
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Relational Operators
> Affects Versions: 1.10.0
> Reporter: Chris Westin
>
> For storage systems like MapR-DB, which don't have a consistent read/snapshot
> model, it's possible for records to change between the time they are found in
> an index, and the time they are looked up in a primary table. If the index is
> being relied upon to satisfy a sort, then it's possible that by the time the
> rows are fetched from the primary table that they are no longer in sorted
> order.
> Sometimes developers depend on an "order by" returning rows in the correct
> order. In order to make sure that happens, there needs to be a per-query
> option to force a sort on the result set in this case.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
