[
https://issues.apache.org/jira/browse/PHOENIX-1015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14052322#comment-14052322
]
rajeshbabu commented on PHOENIX-1015:
-------------------------------------
bq. It's still in the local-index branch, right?
Yes [~jamestaylor].
bq. how about spinning up a pull request for master and giving others a chance
to comment?
I will submit pull request for master(working on this) once this patch gets
committed to local-index branch.
bq. Would you mind filing JIRAs for any outstanding work
I have raised issues to support local index regions split and merges.
bq. Do join queries use local indexes? Any holes there?
Join queries use local indexes only when all columns to project in the
index(same as current behavior). Joining back from main table support is not
done in this patch. Will raise another JIRA and work on it.
bq. For the ReferencingColumn, my preference would be (in a follow up check-in)
to add offset and length parameters to ColumnReference and just have one of
these
+1
bq. if you could make a pass through and add more comments (before we forget
), that would be much appreciated.
Sure James.
Thanks.
> Support joining back to data table row from local index when query condition
> involves leading columns in local index
> --------------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-1015
> URL: https://issues.apache.org/jira/browse/PHOENIX-1015
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: rajeshbabu
> Assignee: rajeshbabu
> Attachments: PHOENIX-1015.patch, PHOENIX-1015_v6.patch,
> PHOENIX-1015_v7.patch, PHOENIX-1015_v8.patch, PHOENIX-1015_v8.rar,
> PHOENIX-1015_v9.patch
>
>
> When a query involves more columns to project than columns in index and query
> condition involves leading columns in local index then first we can get
> matching rowkeys from local index table and then get the required columns
> from data table. In local index both data region and index region co-reside
> in the same RS, we can call get on data region to get the missing columns in
> the index, without any n/w overhead. So it's efficient.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
