[
https://issues.apache.org/jira/browse/PHOENIX-955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-955:
---------------------------------
Attachment: setOffsetOnServerPlusIndexMaintainerChgs.patch
Includes earlier patch plus the change to:
- push whether or not we have a local index to the IndexMaintainer
- prepends the region start key to index rows for local index
[~rajesh23] - let me know if you'd like me to commit this. Barring bugs, this
should take care of the region start key part for ignoring it during
server-side processing and adding it to index rows. Only part left is stripping
the region start key off from rows returned back to the server (which you'd
want to do in ScanRegionObserver - if we can leverage the new Cell interface
and not require a copy of the bytes, that'd be nice).
> Skip region start key at beginning of local index rows
> ------------------------------------------------------
>
> Key: PHOENIX-955
> URL: https://issues.apache.org/jira/browse/PHOENIX-955
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: rajeshbabu
> Assignee: rajeshbabu
> Attachments: setOffsetOnServer.patch,
> setOffsetOnServerPlusIndexMaintainerChgs.patch
>
>
> For co-locating user table regions and index table regions, the index row
> keys will be prepended with the start regions key. We need to skip over this
> in our server-side processing (i.e. mainly when we evaluate a row key
> expression which gets the value of a column that is in the primary key
> constraint and thus part of the row key).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
