You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Kengo Seki (Jira)" <ji...@apache.org> on 2023/10/18 00:07:00 UTC

[jira] [Comment Edited] (BIGTOP-3909) Define Bigtop 3.3 release BOM

    [ https://issues.apache.org/jira/browse/BIGTOP-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17776434#comment-17776434 ] 

Kengo Seki edited comment on BIGTOP-3909 at 10/18/23 12:06 AM:
---------------------------------------------------------------

Here is another proposal. [As I mentioned in the corresponding PR|https://github.com/apache/bigtop/pull/1182#issuecomment-1763534894], upgrading HBase to 2.5.x requires an additional work on the Ranger side (and I don't estimate how heavy it is yet).
But there are still some tough works on Ranger such as BIGTOP-4023, and I wouldn't like to make them blocker for the upcoming release. Is it OK for you to stay HBase 2.4.17 in Bigtop 3.3.0? [~brahmareddy] [~yqGu] [~akankshakedia]


was (Author: sekikn):
Here is another proposal. [As I mentioned in the corresponding PR|https://github.com/apache/bigtop/pull/1182#issuecomment-1763534894], upgrading HBase to 2.5.x requires an additional work on the Ranger side (and I don't estimate how heavy it is).
But there are still some tough works on Ranger such as BIGTOP-4023, and I wouldn't like to make them blocker for the upcoming release. Is it OK for you to stay HBase 2.4.17 in Bigtop 3.3.0? [~brahmareddy] [~yqGu] [~akankshakedia]

> Define Bigtop 3.3 release BOM
> -----------------------------
>
>                 Key: BIGTOP-3909
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-3909
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Yuqi Gu
>            Assignee: Yuqi Gu
>            Priority: Major
>         Attachments: image-2023-09-28-15-57-59-423.png
>
>
> The changes in the next release:
>  * New components like Ranger debian, bigtop-select (for Ambari) would be added into Bigtop support matrix.
>  * Mpack would be removed if Ambari-2.8 was released first which integrated the Bigtop SW stack as its default stack. 
>  * OpenEuler support is under discussion.
>  * Some components needed to be upgraded to fix some issues like gpdb.
> h3. Components
> Let's discuss the component stack of the next release.
> {code:java}
> Components                   in v3.2      in v3.3
> alluxio                        2.8.0  =>  2.9.3
> ambari                         2.7.5  =>  2.8.0
> bigtop-ambari-mpack            2.7.5      Removed
> bigtop-groovy                  2.5.4      2.5.4
> bigtop-jsvc                    1.2.4      1.2.4
> bigtop-utils                   3.1.0      3.1.0
> flink                         1.15.3  =>  1.16.2
> gpdb                          5.28.5  =>  6.23.1
> hadoop                         3.3.4  =>  3.3.6
> hbase                         2.4.13  =>  2.5.3
> hive                           3.1.3      3.1.3 
> kafka                          2.8.1  =>  2.8.2
> livy                           0.7.1  =>  0.8.0
> oozie                          5.2.1      5.2.1
> phoenix                        5.1.2      5.1.3
> ranger                           n/a  =>  2.4.0 
> solr                          8.11.2  =>  9.1.1
> spark                          3.2.3  =>  3.3.3
> tez                           0.10.1  =>  0.10.2
> ycsb                          0.17.0      0.17.0
> zeppelin                      0.10.1      0.10.1
> zookeeper                      3.5.9  =>  3.7.2 (or 3.8.3, if compatible with other components){code}
> h3. Distros
> For reducing the release burden, we could start a discussion about:
>  * Dropping old supported distros 
>  * Only support the latest LTS (CentOS 7 exception)
>  * OpenEuler support
>  
> {code:java}
> - CentOS 7, Rocky Linux 8
> - Debian 11
> - Fedora 38
> - Ubuntu 22.04{code}
> h3. Archs
> {code:java}
> - x86_64
> - Arm64
> - ppc64le {code}
> h3. JDK
> {code:java}
> JDK8
> {code}
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)