[
https://issues.apache.org/jira/browse/PHOENIX-1809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor resolved PHOENIX-1809.
-----------------------------------
Resolution: Fixed
Fix Version/s: 4.4.0
5.0.0
Assignee: James Taylor
Thanks for the review, [~maryannxue]. Pushed to 4.x and master.
> Improve explain plan
> --------------------
>
> Key: PHOENIX-1809
> URL: https://issues.apache.org/jira/browse/PHOENIX-1809
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: James Taylor
> Fix For: 5.0.0, 4.4.0
>
> Attachments: PHOENIX-1809.patch, PHOENIX-1809_v2.patch
>
>
> Two changes:
> 1) We already output the limit information, so it's redundant to display the
> PageFilter filter. Instead we should skip that filter in ExplainTable when we
> generate the explain plan - there are about 5 places in the code that need to
> be changed that expect this in the explain plan.
> 2) Instead of the hacky boolean we pass through MergeSortTopNResultIterator
> to control the output of the server-side order by/limit, we should output
> that information in ExplainTable as well. We'd need to pass through the LIMIT
> information there too. Then the MergeSortTopNResultIterator would only output
> the CLIENT MERGE SORT step.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
