ayushtkn commented on PR #213:
URL: https://github.com/apache/tez/pull/213#issuecomment-1322025347

   Hi @amanraj2520 
   Just curious: What specifically you are targeting from Hadoop-3.3.4, mostly 
there would be some dependency upgrades in 3.3.4 & they must be in sync with 
the versions in current hive master.
   
   Anyway if we plan to do so:
   
   - We would need to upgrade the hadoop version first in master & then only we 
should bring that back to 3.2.0. Any upgrade or fix should go to hive master 
first and then only get backported. So, that is some additional work for you.
   
   - Last time the plan was to move to hadoop-3.3.3, but Tez got issues due to 
some netty version conflict, and that issue wasn't getting flagged in the Hive 
unit tests, but only in actual cluster with Tez, so we should 'confirm' running 
basic tests with Hive before we push for a Tez release, Getting to know "There 
are issues with this version of Hadoop in Hive" once we have a Tez release, 
won't be a good for us, we won't be able to immediately push for a  new Hadoop 
release with the fix, nor a Tez release with the fixed Hadoop release version 
very quickly.
   
   BTW. AFAIK Hadoop-3.3.5 is just awaiting one ABFS related jira fix and 
should be out in a month's time(if no new blockers), We can ask @steveloughran 
if we want to push that quickly for Hive.
   Rest, I am ok with whatever ways you folks feel good, @abstractdog  can help 
share pointers around the timelines for a new Tez release, If we move with 
3.3.4 then I feel moving to 3.3.5 won't be happening any time soon, Getting the 
last Tez release itself was very tough for us.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to