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

Shilun Fan commented on HADOOP-19090:
-------------------------------------

[~pj.fanning] [~ste...@apache.org] 

I am not opposed to releasing hadoop-thirdparty-1.2.1, but I don't think now is 
a good time to do so. If we were to release hadoop-thirdparty-1.2.1, our 
process is too lengthy:

1. We need to announce this in a public mailing list.
2. Then initiate a vote, and after the vote passes, release 
hadoop-thirdparty-1.2.1.
3. Introduce version 1.2.1 in the Hadoop trunk branch.
4. backport hadoop-3.4.0

Even if we upgrade to protobuf-3.23.4, there might still be other issues. If 
there really are other issues, would we need to release hadoop-thirdparty-1.2.2?

I think a better approach would be:

To notify about this in the release email for hadoop-3.4.0, and then release 
hadoop-thirdparty-1.2.1 before the release of hadoop-3.4.1, followed by 
thorough validation.

> Update Protocol Buffers installation to 3.23.4
> ----------------------------------------------
>
>                 Key: HADOOP-19090
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19090
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 3.4.0, 3.3.9
>            Reporter: PJ Fanning
>            Assignee: PJ Fanning
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> We are seeing issues with Java 8 usage of protobuf-java
> See https://issues.apache.org/jira/browse/HADOOP-18197 and comments about
> java.lang.NoSuchMethodError: 
> java.nio.ByteBuffer.position(I)Ljava/nio/ByteBuffer;



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

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to