abstractdog commented on pull request #132:
URL: https://github.com/apache/tez/pull/132#issuecomment-1006885558
thanks @jteagles , I'm about to commit this soon
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
abstractdog commented on pull request #132:
URL: https://github.com/apache/tez/pull/132#issuecomment-1004162107
@jteagles: could you please take a look at the commits?
finally, it looks like we're quite close to the hadoop 3.3.x upgrade,
because several issues were solved in hadoop 3.3.1
abstractdog commented on pull request #132:
URL: https://github.com/apache/tez/pull/132#issuecomment-1003770539
current unit test failure is reproduced as:
```
mvn clean test -Dtest=TestATSHistoryWithACLs#testDAGACls -pl
./tez-plugins/tez-yarn-timeline-history-with-acls
```
rel
abstractdog commented on pull request #132:
URL: https://github.com/apache/tez/pull/132#issuecomment-953249848
new failures are found in ShuffleHandler while running tests:
```
java.lang.NoSuchMethodError:
io.netty.buffer.ByteBuf.forEachByte(Lio/netty/buffer/ByteBufProcessor;)I
abstractdog commented on pull request #132:
URL: https://github.com/apache/tez/pull/132#issuecomment-872089606
> @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 cha
