phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-5300) NoopStatisticsCollector shouldn't scan any rows.
Date Sat, 25 May 2019 00:05:00 GMT

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

Lars Hofhansl commented on PHOENIX-5300:
----------------------------------------

Attaching the same patch again to get another run.

> NoopStatisticsCollector shouldn't scan any rows.
> ------------------------------------------------
>
>                 Key: PHOENIX-5300
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5300
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.14.0, 4.13.1
>            Reporter: Rushabh S Shah
>            Assignee: Rushabh S Shah
>            Priority: Major
>             Fix For: 4.14.2
>
>         Attachments: PHOENIX-5300-4.14-HBase-1.4.patch
>
>
> Today if we disable calculation of stats via {{phoenix.stats.collection.enabled}} property,
it creates {{NoopStatisticsCollector}}. If someone calls "UPDATE STATISTICS <TABLE-NAME>",
it will create NoopStatisticsCollector, scan the whole table and does nothing. This is fixed
in 4.15 via PHOENIX-4009. If we don't want to backport PHOENIX-4009, we can fix this bug just
in 4.14



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

Mime
View raw message