+1 (binding)
Checksum: OK
Signature: OK
mvn install (including test suite): OK
eyeballed changelog: OK
mvn apache-rat:check: OK
Was not able to run the test suite on Mac personally.
best regards
Istvan
On Tue, Jan 30, 2024 at 6:06 AM rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:
>
[
https://issues.apache.org/jira/browse/PHOENIX-4362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajeshbabu Chintaguntla reassigned PHOENIX-4362:
Assignee: Nikita Pande (was: Ankit Singhal)
> Add
As Viraj wrote, those are just plans.
If HBase 3 won't be released by the time the other features are ready, then
it won't make it into 5.3.
If other major features are ready by that time, then they will be included.
(though we are not aware of any now)
As for the new major version, in the past
Please vote on this Apache phoenix omid release candidate,
phoenix-omid-1.1.1RC1
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache phoenix omid 1.1.1
[ ] -1 Do not release this package because ...
The tag to be voted on is 1.1.1RC1:
[
https://issues.apache.org/jira/browse/PHOENIX-7187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikita Pande updated PHOENIX-7187:
--
Description:
Currently in partialIndexIT.java, currently the schema name and table name of
I am not sure how close HBase 3.0 is. Even if it is only less than one
year away, the adoption would be low at the beginning. I don't think 5.3
should wait for that. And traditionally, Phoenix would have a major
release to support the HBase major release (4.x for HBase 1.x and 5.x for
HBase
