[
https://issues.apache.org/jira/browse/PHOENIX-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14483775#comment-14483775
]
Enis Soztutar commented on PHOENIX-1681:
----------------------------------------
bq. What Phoenix branch should we be dev-ing in for HBase 1.1+? I have been
assuming master.
That is not clear at this point. In various threads before, we have discussed
the possibility of having a phoenix branch to work with Hbase-1.1, but there is
no such branch as of now. Master compiles with HBase-1.0. It depends on when
1.1 will arrive and at what release of Phoenix we want to support HBase-1.1. We
need to fork 4.4-HBase-1.0 some time to have a release "4.4.0-HBase-1.0" after
which we can decide to make master point to HBase-1.1+. cc. [~rajeshbabu].
bq. Related, I found an issue addressing NextState related changes:
PHOENIX-1763 .
Thanks for digging that out. I had attached a patch which we maintain
internally. Let me put up the latest version. I can do the changes related to
the new version of HBASE-11544 since I already have some context on the changes
needed (Phoenix has a lot of scanners).
[~jonathan.lawlor] can you please check the latest patch in PHOENIX-1763 to see
the impact of the changes related to NextState. Please take into account that
the NextState creation, etc has to be same visibility scope (LimitedPrivate to
coproc) as the RegionScanner.
> Use the new Region Interface
> ----------------------------
>
> Key: PHOENIX-1681
> URL: https://issues.apache.org/jira/browse/PHOENIX-1681
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Attachments: 0001-PHOENIX-1681-Use-the-new-Region-Interface.patch,
> PHOENIX-1681-4.patch, PHOENIX-1681-4.patch
>
>
> HBase is introducing a new interface, Region, a supportable public/evolving
> subset of HRegion. Use this instead of HRegion in all places where we are
> using HRegion today
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
