Uh oh!
There was an error while loading. Please reload this page.
TEZ-4311: Bump hadoop dependency version to 3.3.x - #132
Conversation
This comment has been minimized.
This comment has been minimized.
belugabehr
commented
Jun 30, 2021
Hey, just FYI. I came across this issue when upgrading Hive 3.3.1: Probably needs to be handled by Tez unless HADOOP-17779 is accepted (and released in a subsequent version). |
jteagles
commented
Jun 30, 2021
@abstractdog, if we are to start hadoop 3.3 changes we should consider branching branch-0.10. Here's a thought. Instead of calling it 0.11 for hadoop 3.3 support, what if we change version on master to 3.3 to reflect hadoop compatibility. |
abstractdog
commented
Jul 1, 2021
I like the idea, especially because tez is battle-tested and stable for a very long time, deserves more than 0.x |
belugabehr
commented
Jul 1, 2021
Hey Guys, I would be careful hitching the wagon to any other projects. I think it's helpful to be on your own release cadence. However, I think 1.0 is a good first step and would lead the way to some more thoughtful approach to backwards compatibility and stableness (not that these things aren't true now, but it make it more formalized for new folks). Thanks. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
new failures are found in ShuffleHandler while running tests: full log file is attached to JIRA: https://issues.apache.org/jira/secure/attachment/13035409/org.apache.tez.auxservices.TestShuffleHandler-output.txt |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
abstractdog
commented
Jan 2, 2022
current unit test failure is reproduced as: related to YARN-9554, it's under investigation |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
tez-yetus
commented
Jan 3, 2022
🎊 +1 overall
This message was automatically generated. |
abstractdog
commented
Jan 3, 2022
@jteagles: could you please take a look at the commits? |
jteagles
left a comment
There was a problem hiding this comment.
+1. I feel we are ready for this change. Probably we should plan a release once we can certify
thanks @jteagles, I'm about to commit this soon |
No description provided.