[
https://issues.apache.org/jira/browse/PHOENIX-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16447052#comment-16447052
]
James Taylor commented on PHOENIX-4686:
---------------------------------------
FYI, see attached patch, [~abhishek.chouhan]. This patch:
* Calculates estimates when there's a limit pushed to the server (and no where
clause)
* Introduces a new timestamp constant that indicates that the estimates aren't
based on statistics (i.e. they're based on the limit clause in the query so
they'll never change based on statistics).
Still needs a couple of tests.
> Phoenix stats does not account for server side limit push downs
> ---------------------------------------------------------------
>
> Key: PHOENIX-4686
> URL: https://issues.apache.org/jira/browse/PHOENIX-4686
> Project: Phoenix
> Issue Type: Bug
> Reporter: Abhishek Singh Chouhan
> Assignee: Abhishek Singh Chouhan
> Priority: Major
> Attachments: PHOENIX-4686-wip.master.patch, PHOENIX-4686_wip1.patch
>
>
> For a query like SELECT * FROM FOO LIMIT 10 the EST_BYTES_READ does not take
> into account a limit correctly when there's no WHERE clause (or a WHERE
> clause that gets compiled out into start/stop row key on the scan).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
