Aggarwal-Raghav commented on PR #474:
URL: https://github.com/apache/tez/pull/474#issuecomment-4681507234

   @maheshrajus , there are 2 things here.
   1. javax error, i think its valid as hadoop 
https://github.com/apache/hadoop/blame/9b71e5f0c0db40e498b6eb4a11f7fe531cadcc9a/hadoop-project/pom.xml#L954
 updated this for jersey 2.x change and I think this patch will help: 
[javax.patch](https://github.com/user-attachments/files/28842187/javax.patch)  
logs from my run: 
[logs.txt](https://github.com/user-attachments/files/28841838/logs.txt)
   
   3. jackson issue, and the patch for it: 
[jackson.patch](https://github.com/user-attachments/files/28842213/jackson.patch)
 logs: 
[logs2_jackson.txt](https://github.com/user-attachments/files/28841823/logs2_jackson.txt)
   
   The patch attached is how I would've handled it. Your jackson change is 
indeed required which was part of my future pr in hadoop-3.5.0, so I'm ok with 
that but exclusion from pig is required which is bringing jackson `1.8.8`. This 
might also infer Pig might break but I think it should be ok as its legacy 
project: 
https://github.com/apache/tez/pull/490/changes#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8e4d8R278
 
   CC @abstractdog 
   
   I got both the issue in my run and post that attaching the clean logs as 
well 
[clean_log.txt](https://github.com/user-attachments/files/28842257/clean_log.txt).
 I have `verbose:class` in the tez-opts to see from which jar the class is 
getting loaded. For javax it was `servlet-2.x` and `jackson 2.14.3` coming from 
avro which is transitive in hadoop-common dependency as you mentioned in 
comments. Even after exclusion of avro from hadoop-common the avro jar is part 
of tarball which is good as we are not shipping less jars.


-- 
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