[
https://issues.apache.org/jira/browse/PHOENIX-1475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224051#comment-14224051
]
ramkrishna.s.vasudevan commented on PHOENIX-1475:
-------------------------------------------------
bq.For example, if a major compaction runs, you should still be able to run
UPDATE STATISTICS immediately afterwards.
Yes [~giacomotaylor]. I think while developing this feature we encountered this
scenario and that time the code was having some clearCache call just after
major compaction was done. (I don't remember that now).
So coming to have we will differentiate a stats update thro major compaction
and the one by UPDATE STATS query?
Will we have some flag to indicate it? Currently there is no means to
differentiate it I suppose. So the latest row that we retrieve from the STATS
table if it is having a TYPE that could act as an indicator.
> Statistics are not immediately used after data load
> ---------------------------------------------------
>
> Key: PHOENIX-1475
> URL: https://issues.apache.org/jira/browse/PHOENIX-1475
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.2
> Reporter: Mujtaba Chohan
> Assignee: James Taylor
> Priority: Minor
>
> Although statistics are available in stats table but they are not used when
> query is executed immediately after data is loaded in a table. Also _update
> statistics_ cannot be executed since _phoenix.stats.minUpdateFrequency_ has
> not elapsed nor are they are used immediately after running _major
> compaction_.
> Stats are used after _phoenix.stats.updateFrequency_ has elapsed but there is
> no way to force immediate use for uses cases such as performance test
> utilities and real time systems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
