phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4333) Incorrect estimate when stats are updated on a tenant specific view
Date Tue, 27 Feb 2018 22:56:00 GMT

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

Hudson commented on PHOENIX-4333:
---------------------------------

SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-0.98 #1822 (See [https://builds.apache.org/job/Phoenix-4.x-HBase-0.98/1822/])
PHOENIX-4333 Incorrect estimate when stats are updated on a tenant (jtaylor: rev 48e4980b7efd8202fa36270eb7d9827f9cde828e)
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/ExplainPlanWithStatsEnabledIT.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/iterate/BaseResultIterators.java


> 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, 5.0.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)

Mime
View raw message