[
https://issues.apache.org/jira/browse/HBASE-29302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953232#comment-17953232
]
Nihal Jain edited comment on HBASE-29302 at 5/21/25 6:59 PM:
-------------------------------------------------------------
Thank you [~ndimiduk] and [~zhangduo] for the reference, I have been able to
publish the keys at [https://dist.apache.org/repos/dist/release/hbase/KEYS]
{quote}Do we still need to use older jetty for branch-3+? If not, I prefer we
make a new branch for branch-2.x, and bump the version in master branch to 5.x.
{quote}
No we will completely drop usage of older jetty9 from master and be only on
jetty12, you can refer PR with the proposed change
[https://github.com/apache/hbase/pull/6783]
So as I understand we are looking to create 2 branches for hbase-thirdparty:
* Master which will be 5.x and be used by hbase-3+
** will contain jetty12 changes
** also we plan to make hbase-unsafe support jdk17 here, eventually?
** so basically eventually we will move to JDK 17 for this branch
* Fork current master as 4.x and this will be used by hbase-2.x
** will continue to be on jetty9
** this will still be using JDK8
I see we would double up maintenance with this as now we have to drive 2
releases for hbase-thirdparty and also each PR needs to be backported
appropriately.
Apart from JDK17, I am not sure how this will be useful as we can still have
multiple modules some being used by hbase-2.x while others used by 3.x+
Is my understanding correct? Should we start a discuss thread for this?
CC: [~stoty]
was (Author: nihaljain.cs):
Thank you [~ndimiduk] and [~zhangduo] for the reference, I have been able to
publish the keys at [https://dist.apache.org/repos/dist/release/hbase/KEYS]
{quote}Do we still need to use older jetty for branch-3+? If not, I prefer we
make a new branch for branch-2.x, and bump the version in master branch to 5.x.
{quote}
No we will completely drop usage of older jetty9 from master and be only on
jetty12, you can refer PR with the proposed change
[https://github.com/apache/hbase/pull/6783]
So as I understand we are looking to create 2 branches for hbase-thirdparty:
* Master which will be 5.x and be used by hbase-3+
*
** will contain jetty12 changes
** also we plan to make hbase-unsafe support jdk17 here, eventually?
** so basically eventually we will move to JDK 17 for this branch
* Fork current master as 4.x and this will be used by hbase-2.x
** will continue to be on jetty9
** this will still be using JDK8
I see we would double up maintenance with this as now we have to drive 2
releases for hbase-thirdparty and also each PR needs to be backported
appropriately.
Apart from JDK17, I am not sure how this will be useful as we can still have
multiple modules some being used by hbase-2.x while others used by 3.x+
Is my understanding correct? Should we start a discuss thread for this?
CC: [~stoty]
> [hbase-thirdparty] Release hbase-thirdparty 4.1.11
> --------------------------------------------------
>
> Key: HBASE-29302
> URL: https://issues.apache.org/jira/browse/HBASE-29302
> Project: HBase
> Issue Type: Umbrella
> Components: community, thirdparty
> Reporter: Nihal Jain
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
