Github user ramkrish86 commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/8#discussion_r16699028
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataEndpointImpl.java
---
@@ -1594,4 +1775,46 @@ public boolean filterRowKey(byte[] buffer, int
offset, int length) {
return cmp != 0;
}
}
+ /**
+ * A thread (Chore) that keeps reading the updated stats and
invalidates the Meta cache incase there is
+ * a change in the stats
+ */
+ private static class StatisticsUpdator extends Chore {
--- End diff --
I think all this periodic checking of stats table itself wont't be needed
is what you mean? So my doubt is this suppose I have some select queries coming
periodically to a table and there are updations also happening to that table,
if we are able to collect the stats periodically, for the newer select queries
we would be able to use the udpated information right? Only if we collect the
stats during re-load it would mean that if there is no schema change or index
addition/deletion the updated stats info may not be used. For me I think
periodic updation of the stats would be a better choice.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
