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

James Taylor commented on PHOENIX-4333:
---------------------------------------

Please review, [~tdsilva]. If you have spare cycles to take a look too, 
[~samarthjain], that'd be much appreciated. The basic idea of the patch is to 
detect if we encounter a region with no guideposts, and if so, then we set the 
estimated timestamp to null. This covers the issue described for this JIRA. 
Also, some edge cases are now accounted for: namely when the guidepost is equal 
to the start key of the scan or equal to the end region key.

> Incorrect estimate when stats are updated on a tenant specific view
> -------------------------------------------------------------------
>
>                 Key: PHOENIX-4333
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4333
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.12.0
>            Reporter: Mujtaba Chohan
>            Assignee: James Taylor
>            Priority: Major
>              Labels: SFDC, stats
>             Fix For: 4.14.0
>
>         Attachments: PHOENIX-4333_test.patch, PHOENIX-4333_v1.patch, 
> PHOENIX-4333_v2.patch, PHOENIX-4333_v3.patch, PHOENIX-4333_wip1.patch, 
> PHOENIX-4333_wip2.patch, PHOENIX-4333_wip3.patch, PHOENIX-4333_wip4.patch
>
>
> Consider two tenants A, B with tenant specific view on 2 separate 
> regions/region servers.
> {noformat}
> Region 1 keys:
> A,1
> A,2
> B,1
> Region 2 keys:
> B,2
> B,3
> {noformat}
> When stats are updated on tenant A view. Querying stats on tenant B view 
> yield partial results (only contains stats for B,1) which are incorrect even 
> though it shows updated timestamp as current.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to