Bodor Laszlo

thanks @ayushtkn! can I have a committer approval on this @rbalamohan? tez 0.10.2 is already released, this is just the usual post-release work

yes, let me check this PR and have some test coverage

left some comments also, could you please make a simple validity check with javadocs on JDK17? ``` mvn javadoc:javadoc #take a look at for example tez-api/target/site/apidocs/index.html ```

I think the error is because currently, we don't use a Jenkinsfile in the repo, but tez-multibranch job ([link](https://ci-hadoop.apache.org/job/tez-multibranch/)) has the --findbugs-strict-precheck flag, which is not handled then(once we'll have...

@jteagles : I was already looking at that patch, looks good, I'm about to adopt it piece-by-piece

@belugabehr, please rebase this PR as TEZ-4290 is merged, you might have minimal conflicts with that in Dockerfile

@belugabehr: could you please refresh/rebase this PR? considering that Jenkinsfile and github integration is working for a long time, we can retry this initiative

thanks guys for taking care of security issues in Tez! I can see that TEZ-4419 is an umbrella with lots of subtasks if we're tracking fixes on separate jiras, we...

thanks for this patch @zhengchenyu! can you include a unit test to TestTaskScheduler which confirms that a TaskScheduler returns Resource(0,0) even if the RM client returned null? I'm not familiar...

thanks @zhengchenyu, after reading YARN-8933 this definitely makes sense I don't insist on adding a unit test as we're "fixing" a yarn issue here, which is not present anymore after...