You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2014/12/30 07:58:13 UTC

[jira] [Updated] (PHOENIX-1511) Invalidate stats row even if not running stats due to phoenix.stats.minUpdateFrequency

     [ https://issues.apache.org/jira/browse/PHOENIX-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Taylor updated PHOENIX-1511:
----------------------------------
    Attachment: PHOENIX-1511.patch

[~mujtabachohan] - this patch addresses the problem you found in which after running a major compaction, you were forced to wait to see the stats updated on the client. With this patch, regardless of the setting of phoenix.stats.minUpdateFrequency, you could
- run a major compaction
- immediately call update stats
- run a query which would use the updated stats

Please let me know if this addresses the issue you found.

> Invalidate stats row even if not running stats due to phoenix.stats.minUpdateFrequency
> --------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-1511
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1511
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>         Attachments: PHOENIX-1511.patch
>
>
> This will allow the client to see the new/potentially recently updated stats values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)