You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2019/05/24 18:47:00 UTC
[jira] [Updated] (PHOENIX-5300) NoopStatisticsCollector shouldn't
scan any rows.
[ https://issues.apache.org/jira/browse/PHOENIX-5300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated PHOENIX-5300:
------------------------------------
Fix Version/s: 4.15.0
> 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.15.0, 4.14.2
>
>
> 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)