Apache Ozone -1.4. Upgrading parcel version to include latest backports

[#1]

We've encountered an issue within Apache Ozone (1.4.0 and 1.4.1) which we believe are related to HDDS-9967

A fix for this particular issue has now been backported to the 'apache:ozone-1.4' project as part of pull request https://github.com/apache/ozone/pull/9066

How do we update the Cloudera Runtime or Ozone parcel version (1.4.0.7.1.9.1054-4) to include this fix? Upgrading to the latest 1.4.2 would be ideal.

Thanks Stephen

[#2]

Hello @SKERR 

Thank you for reaching out to the Cloudera community

Could you please confirm what CDP version you are using currently?

Additionaly you can check the component version offered by cloudera in CDP versions using the below links

https://docs.cloudera.com/cdp-private-cloud-base/7.3.1/private-release-notes/topics/rt-runtime-compo...

[#3]

Hey @upadhyayk04  appreciate the response. 

I have access to both CDP 7.1.9 and 7.3.1 clusters in a testing ENV.

• 7.1.9 SP1 CHF 11 - with Apache Ozone: (1.4.0.7.1.9.1059-4)
• 7.3.1.400 SP2 - with Apache Ozone: (7.3.1.100 and higher - 1.4.0.7.3.1.100-39)

I'd like to know if its possible to upgrade the Apache Ozone version - from 1.4.0 to 1.4.2 in one or both of these ENVs?

Thanks Stephen

[#4 · Accepted solution]

Hello @SKERR 

No direct component upgrade is supported. However, I could see that the JIRA mentioned by you is already fixed in CDP 7.3.1  

https://docs.cloudera.com/cdp-private-cloud-base/7.3.1/private-release-notes/topics/rt-fixed-issues-...

[#5]

@upadhyayk04 - thanks will upgrade the runtime version.