[
https://issues.apache.org/jira/browse/PHOENIX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301119#comment-15301119
]
Nick Dimiduk commented on PHOENIX-258:
--------------------------------------
In my particular case, itemizing the leading column also allows phoenix to take
advantage of more of the rowkey as an index, so without the 'in' clause, my
explain is
{noformat}
CLIENT 51739-CHUNK PARALLEL 51739-WAY RANGE SCAN
{noformat}
while including the 'in' clause
{noformat}
CLIENT 995-CHUNK PARALLEL 995-WAY SKIP SCAN ON 140 RANGES
{noformat}
> Use skip scan when SELECT DISTINCT on leading row key column(s)
> ---------------------------------------------------------------
>
> Key: PHOENIX-258
> URL: https://issues.apache.org/jira/browse/PHOENIX-258
> Project: Phoenix
> Issue Type: Task
> Reporter: ryang-sfdc
> Labels: gsoc2016
> Fix For: 4.8.0
>
> Attachments: 258.txt, DistinctFixedPrefixFilter.java, in-clause.png
>
>
> create table(a varchar(32) not null, date date not null constraint pk primary
> key(a,date))
> [["PLAN"],["CLIENT PARALLEL 94-WAY FULL SCAN OVER foo"],[" SERVER
> AGGREGATE INTO ORDERED DISTINCT ROWS BY [a]"],["CLIENT MERGE SORT"]]
>
> We should skip scan.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
