[
https://issues.apache.org/jira/browse/PHOENIX-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235245#comment-16235245
]
Samarth Jain commented on PHOENIX-4333:
---------------------------------------
It might be a late night and lack of coffee but I am not sure I see the
co-relation here.
{code}
gpsAvailableForAllRegions &= initialKeyBytes != currentKeyBytes;
{code}
We set initialKeyBytes to currentKeyBytes when we know we are not using stats
for parallelisation.
{code}
if (!useStatsForParallelization) {
/*
* If we are not using stats for generating parallel scans,
we need to reset the
* currentKey back to what it was at the beginning of the
loop.
*/
currentKeyBytes = initialKeyBytes;
}
{code}
bq. I also think we should set the estimatedRows and estimatedSize to what
we've found, but only set estimateInfoTimestamp to null if
!gpsAvailableForAllRegions. That way callers can choose to use or not use the
partial estimates based on estimateInfoTimestamp.
Makes sense.
> Stats - 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: Samarth Jain
> Priority: Major
> Attachments: PHOENIX-4333_test.patch, PHOENIX-4333_v1.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
(v6.4.14#64029)
