Hi Sanjay,
I have different opinions about what's important and how to eventually
integrate this code, and that's not because I'm "conveniently ignoring"
your responses. I'm also not making some of the arguments you claim I am
making. Attacking arguments I'm not making is not going to change my mi
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/151/
[Mar 1, 2018 5:24:17 AM] (haibochen) YARN-7835. Race condition in NM while
publishing events if second
[Mar 1, 2018 10:04:57 AM] (aajisaka) HADOOP-15275. Incorrect javadoc for return
type of
-1 overa
I’m generally neutral and looked foremost at developer impact. Ie. Will
it be so intertwined with hdfs that each project risks destabilizing the
other? Will developers with no expertise in ozone will be impeded? I
think the answer is currently no. These are the intersections and some
concerns
I think it would be good to get this in sooner rather than later, but I
have some thoughts.
1. It is hard to tell what has changed. git rebase -i tells me the
branch has 722 commits. The rebase failed with a conflict. It would really
help if you rebased to current trunk.
2. I think Ozo
Oops, retrying now subscribed to more than solely yarn-dev.
-Clay
On Wed, 28 Feb 2018, Clay B. wrote:
+1 (non-binding)
I have walked through the code and find it very compelling as a
user; I really look forward to seeing the Ozone code mature and
it maturing HDFS features together. The poin
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/707/
[Feb 28, 2018 2:17:43 AM] (yqlin) HDFS-13194. CachePool permissions incorrectly
checked. Contributed by
[Feb 28, 2018 9:58:09 AM] (wwei) YARN-7929. Support to set container execution
type in SLS. (Jiandan
