phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cody Marcel (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (PHOENIX-4686) Phoenix stats does not account for server side limit push downs
Date Tue, 24 Apr 2018 16:27:01 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16450154#comment-16450154
] 

Cody Marcel edited comment on PHOENIX-4686 at 4/24/18 4:26 PM:
---------------------------------------------------------------

> "Calculates estimates when there's a limit pushed to the server (and no where clause)"

The original issue was a LIMIT in conjunction with a WHERE IN clause. Can we confirm this
will fix that issue as well?


was (Author: cody.marcel@gmail.com):
> "Calculates estimates when there's a limit pushed to the server (and no where clause)"

The original issue was a LIMIT in conjunction with a WHERE IN clause. Can we confirm this
will fix that issue as well

> 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.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)

Mime
View raw message