[jira] [Updated] (PHOENIX-4686) Phoenix stats does not account for server side limit push downs
[ https://issues.apache.org/jira/browse/PHOENIX-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4686: -- Attachment: PHOENIX-4686_v2.patch > 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)
[jira] [Updated] (PHOENIX-4686) Phoenix stats does not account for server side limit push downs
[ https://issues.apache.org/jira/browse/PHOENIX-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4686: -- Attachment: (was: PHOENIX-4686_v2.patch) > 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)
[jira] [Updated] (PHOENIX-4686) Phoenix stats does not account for server side limit push downs
[ https://issues.apache.org/jira/browse/PHOENIX-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4686: -- Attachment: PHOENIX-4686_v2.patch > 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)
[jira] [Updated] (PHOENIX-4686) Phoenix stats does not account for server side limit push downs
[ https://issues.apache.org/jira/browse/PHOENIX-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4686: -- Fix Version/s: 5.0.0 4.14.0 > 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_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)
[jira] [Updated] (PHOENIX-4686) Phoenix stats does not account for server side limit push downs
[ https://issues.apache.org/jira/browse/PHOENIX-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-4686: Attachment: PHOENIX-4686.master.patch > 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)
[jira] [Updated] (PHOENIX-4686) Phoenix stats does not account for server side limit push downs
[ https://issues.apache.org/jira/browse/PHOENIX-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor updated PHOENIX-4686: -- Attachment: PHOENIX-4686_wip1.patch > 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)
[jira] [Updated] (PHOENIX-4686) Phoenix stats does not account for server side limit push downs
[ https://issues.apache.org/jira/browse/PHOENIX-4686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Singh Chouhan updated PHOENIX-4686: Attachment: PHOENIX-4686-wip.master.patch > 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 > > > 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)
