[
https://issues.apache.org/jira/browse/PHOENIX-6211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kadir OZDEMIR updated PHOENIX-6211:
-----------------------------------
Description: Phoenix performs two main operations on the server side:
aggregation and filtering. However, currently there is no internal Phoenix
paging capability, and thus server side operations can take long enough to lead
to HBase client timeouts. PHOENIX-5998 and PHOENIX-6207 are for providing the
paging capability for ungrouped and grouped aggregate operations. This
improvement Jira is for adding the paging capability for scan filters. (was:
Phoenix performs two main operations on the server side: aggregation and
filtering. However, currently there is no internal Phoenix paging capability,
and thus server side operations can take long enough lead to HBase client
timeouts. PHOENIX-5998 and PHOENIX-6207 are for providing the paging capability
for ungrouped and grouped aggregate operations. This improvement Jira is for
adding the paging capability for scan filters. )
> Paged scan filters
> ------------------
>
> Key: PHOENIX-6211
> URL: https://issues.apache.org/jira/browse/PHOENIX-6211
> Project: Phoenix
> Issue Type: Improvement
> Affects Versions: 5.0.0, 4.14.3
> Reporter: Kadir OZDEMIR
> Assignee: Kadir OZDEMIR
> Priority: Major
> Fix For: 4.16.0
>
>
> Phoenix performs two main operations on the server side: aggregation and
> filtering. However, currently there is no internal Phoenix paging capability,
> and thus server side operations can take long enough to lead to HBase client
> timeouts. PHOENIX-5998 and PHOENIX-6207 are for providing the paging
> capability for ungrouped and grouped aggregate operations. This improvement
> Jira is for adding the paging capability for scan filters.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
