[
https://issues.apache.org/jira/browse/PHOENIX-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250370#comment-14250370
]
stack commented on PHOENIX-1536:
--------------------------------
bq. I would argue the current local indexing implementation is unsupportable. I
don't think we should advise users to rely on local indexes until we have an
implementation that isn't based on reaching into the private parts of HBase.
I support the [~apurtell] position above. Sean and Elliott say it well over in
HBASE-12566 (When fellas state a position cleanly, no need for others to pile
on). Phoenix cannot change HBase fundamental operation (even selectively)
adding a feature. The recent reluctant change to SplitTransaction to get
[~rajesh23] out of a bind should not be interpreted as license to continue
reaching into HBase internals. Lets work on getting Phoenix on the other side
of agreed-upon APIs (not private HBase internal APIs). It'll be better for
both projects going forward.
> Make use of SplitTransaction to split local index region from 0.98.9 onwards
> ----------------------------------------------------------------------------
>
> Key: PHOENIX-1536
> URL: https://issues.apache.org/jira/browse/PHOENIX-1536
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.2.2
> Reporter: Rajeshbabu Chintaguntla
> Fix For: 5.0.0, 4.3
>
> Attachments: PHOENIX-1536.patch
>
>
> Currently we are using IndexSpilitTransaction which is duplicate of
> SplitTransaction with minor changes. From 0.98.9 onwards we can use the
> SplitTransaction itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)