[
https://issues.apache.org/jira/browse/PHOENIX-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14250398#comment-14250398
]
James Taylor commented on PHOENIX-1536:
---------------------------------------
I agree that the HBase community and Phoenix community should work together
closely and come up with good agreed on APIs.
I'm not arguing whether or not local indexing is supportable (you guys know
that far better than I). I'm saying that local indexing went through a lengthy
review processes in Phoenix back in July - everyone had an opportunity to voice
their opinion then. It made it into the 4.0 release and has seen continued
improvements in 4.1 and 4.2. Users are already using on it and relying on it.
The time to have the discussion of including or not including that feature
sailed a while back.
How about we focus on figuring out a good API story and allow local indexing to
improve in Phoenix until the two can come together? The soonest that'll happen
is when HBase 1.0 comes out? Or are we talking 2.0 now?
> 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)
