[
https://issues.apache.org/jira/browse/PHOENIX-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16453309#comment-16453309
]
Cody Marcel edited comment on PHOENIX-4686 at 4/26/18 1:01 AM:
---------------------------------------------------------------
We'd need to handle both cases with correct stats. We'd expect stats to match
the the explain plan for limit push downs.
WHERE pkcol IN ('A', 'B') LIMIT N
WHERE nonpkcol IN ('A', 'B') LIMIT N
was (Author: cody.mar...@gmail.com):
We'd need to handle both cases with correct stats.
WHERE pkcol IN ('A', 'B') LIMIT N
WHERE nonpkcol IN ('A', 'B') LIMIT N
> 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
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4686-wip.master.patch,
> PHOENIX-4686.master.patch, PHOENIX-4686_v2.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)
