[
https://issues.apache.org/jira/browse/PHOENIX-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234965#comment-14234965
]
James Taylor commented on PHOENIX-1312:
---------------------------------------
The same rules apply here as with PHOENIX-654 in terms of when the empty key
value must be projected. [~ramkrishna] - currently (because of this) Phoenix
will never use stats other than the stats associated with the empty key value
column family. This would be an easy issue to fix and would get the other stats
we're calculating to be used (which would be a big perf boost in certain cases).
> Do not always project the empty column family
> ---------------------------------------------
>
> Key: PHOENIX-1312
> URL: https://issues.apache.org/jira/browse/PHOENIX-1312
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
>
> Often times, we don't need to, but it seems we always are. See
> MultiCfQueryExecIT.testGuidePostsForMultiCFs() where we run a query like this:
> {code}
> SELECT count(*) FROM multi_cf WHERE e.cpu_utilization IS NOT NULL
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
