[ 
https://issues.apache.org/jira/browse/PHOENIX-7701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tanuj Khurana updated PHOENIX-7701:
-----------------------------------
    Description: When paging times out in UngroupedAggregateRegionScanner, the 
scanner checks if it has already counted some rows. If so, it returns the 
current count. If not, it returns a dummy result. As part of PHOENIX-5117 , we 
mark the flag on the ScannerContext to return response to the client 
immediately only for a dummy result. However, if paging timeout happens but a 
valid result is returned instead, then we do not force for immediate return 
currently. The fix is to set the ScannerContext in that case too.  (was: When 
paging times out in UngroupedAggregateRegionScanner, the scanner checks if it 
has already counted some rows. If so, it returns the current count. If not, it 
returns a dummy result. As part of 
[PHOENIX-5117|https://issues.apache.org/jira/browse/PHOENIX-5117]  we mark the 
flag on the ScannerContext to return response to the client immediately only 
for a dummy result. However, if paging timeout happens but a valid result is 
returned instead, then we do not force for immediate return currently.)

> UngroupedAggregateRegionScanner doesn't release rpc handler on page timeouts
> ----------------------------------------------------------------------------
>
>                 Key: PHOENIX-7701
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-7701
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Tanuj Khurana
>            Priority: Major
>
> When paging times out in UngroupedAggregateRegionScanner, the scanner checks 
> if it has already counted some rows. If so, it returns the current count. If 
> not, it returns a dummy result. As part of PHOENIX-5117 , we mark the flag on 
> the ScannerContext to return response to the client immediately only for a 
> dummy result. However, if paging timeout happens but a valid result is 
> returned instead, then we do not force for immediate return currently. The 
> fix is to set the ScannerContext in that case too.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to