+1
-Dinesh
On Sun, Oct 27, 2019, 4:25 AM Elek, Marton
> As discussed earlier in the thread of "Hadoop-Ozone repository mailing
> list configurations" [1] I suggested to solve the current
> misconfiguration problem with creating separated mailing lists
> (dev/issues) for Hadoop Ozone.
>
> It w
+1
-Ayush
> On 27-Oct-2019, at 1:55 PM, Elek, Marton wrote:
>
>
> As discussed earlier in the thread of "Hadoop-Ozone repository mailing list
> configurations" [1] I suggested to solve the current misconfiguration problem
> with creating separated mailing lists (dev/issues) for Hadoop Ozone.
Ah! Yes! That makes sense. I will use the mapredonhdfs framework in my next
set of tests.
The other compatibility tests that I ran worked as expected.
-Eric
On Saturday, October 26, 2019, 12:29:54 PM CDT, Jonathan Hung
wrote:
Hi Eric, I took a quick look, are you using
mapreduce.appl
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1302/
No changes
-1 overall
The following subsystems voted -1:
asflicense findbugs hadolint pathlen unit xml
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc checks
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/487/
No changes
-1 overall
The following subsystems voted -1:
asflicense findbugs hadolint pathlen unit xml
The following subsystems voted -1 but
were configured to be filtered/ignored:
cc check
As discussed earlier in the thread of "Hadoop-Ozone repository mailing
list configurations" [1] I suggested to solve the current
misconfiguration problem with creating separated mailing lists
(dev/issues) for Hadoop Ozone.
It would have some additional benefit: for example it would make eas
