[
https://issues.apache.org/jira/browse/PHOENIX-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15057570#comment-15057570
]
James Taylor commented on PHOENIX-1312:
---------------------------------------
One other improvement you can make is in BaseResultIterators.getGuidePosts().
We're using the existence of the defaultCF in scan.getFamilyMap(), but this
includes *both* column families in the SELECT expressions as well as in the
WHERE clause. We really only care about the ones in the WHERE clause for
parallelization, so it'd be better if we only considered those. Those are the
ones in {{context.getWhereCoditionColumns()}}, though this contains cf.cq
pairs, you could turn it into a Set<byte[]> for this call's usage.
> 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
> Assignee: ramkrishna.s.vasudevan
> Fix For: 4.7.0
>
> Attachments: PHOENIX-1312_1.patch, PHOENIX-1312_v2.patch,
> Phoenix-1312.patch
>
>
> 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)
