Thanks to report this problem Rohith,
Yes, it seems to be configured with the wrong mailing list.
I think the right fix is to create ozone-dev@ and ozone-issues@ and use
them instead of hdfs-(dev/issues).
Is there any objections against creating new ozone-* mailing lists?
Thanks,
Marton
On 10/21/19 6:03 AM, Rohith Sharma K S wrote:
+ common/yarn and mapreduce/submarine
Looks like same issue in submarine repository also !
On Mon, 21 Oct 2019 at 09:30, Rohith Sharma K S <rohithsharm...@apache.org>
wrote:
Folks,
In Hadoop world, any mailing list has its own purposes as below
1. hdfs/common/yarn/mapreduce-*dev *mailing list is meant for developer
discussion purpose.
2. hdfs/common/yarn/mapreduce*-issues* mailing list used for comments
made in the issues.
It appears Hadoop-Ozone repository configured *hdfs-dev *mailing list
for *hdfs-issues* list also. As a result hdfs-dev mailing list is
bombarded with every comment made in hadoop-ozone repository.
Could it be fixed?
-Rohith Sharma K S
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-h...@hadoop.apache.org
