You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by Akira Ajisaka <aa...@gmail.com> on 2019/02/14 06:18:49 UTC
Re: [DISCUSS] Removal of old hamlet package in 3.3+ or 3.4+
Thanks Masatake for your comments.
Added the other Hadoop mailing lists to Cc.
> I'm +1 on making imcompatible change if this blocks another Java migration issues, while I don't see strong reason to hurry as I see the patch of YARN-9279.
Agreed.
-Akira
On Sun, Feb 10, 2019 at 2:00 AM Masatake Iwasaki
<iw...@oss.nttdata.co.jp> wrote:
>
> Thanks for working on this, Akira.
>
> > The only usage I can see is Apache Slider, however, the
> > functionalities of Apache Slider have been merged into YARN.
>
> Do we have mailing lists other than yarn-dev to reach downstream developers?
> It would be better to make it confident that old hamlet of Hadoop 3 is
> used nowhere.
>
> I'm +1 on making imcompatible change if this blocks another Java
> migration issues,
> while I don't see strong reason to hurry as I see the patch of YARN-9279.
>
> Masatake Iwasaki
>
> On 2/3/19 18:10, Akira Ajisaka wrote:
> > Filed https://issues.apache.org/jira/browse/YARN-9279 to remove the
> > old hamlet package.
> >
> > -Akira
> >
> > 2019年1月21日(月) 13:08 Akira Ajisaka <aa...@apache.org>:
> >> Hi folks,
> >>
> >> I'd like to remove the deprecated hamlet package to reduce the maintenance cost.
> >>
> >> The old hamlet package has one character '_' and it is banned in Java
> >> 9+, so HADOOP-11875 deprecated this package and created a profile in
> >> pom.xml not to compile the package when the Java version is 9+. After
> >> the deprecation, we still have to maintenance the profile (see
> >> YARN-8123 and HADOOP-16046).
> >>
> >> The only usage I can see is Apache Slider, however, the
> >> functionalities of Apache Slider have been merged into YARN. Therefore
> >> I think there are no people using Slider with Hadoop 3.1+ and we can
> >> remove the package in 3.3+.
> >>
> >> Any thoughts?
> >>
> >> Regards,
> >> Akira
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: [DISCUSS] Removal of old hamlet package in 3.3+ or 3.4+
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
I'm basically +1 on removing the package.
The patch of YARN-9279 is still applicable to trunk.
If we are still unable to remove the package due to downstream projects,
another option could be always excluding the hamlet package from javadoc
build
as done in java9 profile only now?
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<excludePackageNames>org.apache.hadoop.yarn.webapp.hamlet</excludePackageNames>
</configuration>
</plugin>
On 2020/01/15 13:36, Akira Ajisaka wrote:
> Hi folks,
>
> Now I have a strong reason to remove the old hamlet package.
>
> There are 1000+ javadoc warnings in the package and they fill the output of
> the precommit javadoc module.
> That's why the new warnings and errors are ignored and sometimes they cause
> build errors.
>
> Now I'm investigating why the precommit job ignores new javadoc
> warnings/errors
> in https://issues.apache.org/jira/browse/HADOOP-16802. I'd like to remove
> the package to make the investigation easier.
>
> Regards,
> Akira
>
> On Thu, Feb 14, 2019 at 3:18 PM Akira Ajisaka <aa...@gmail.com> wrote:
>
>> Thanks Masatake for your comments.
>> Added the other Hadoop mailing lists to Cc.
>>
>>> I'm +1 on making imcompatible change if this blocks another Java
>> migration issues, while I don't see strong reason to hurry as I see the
>> patch of YARN-9279.
>> Agreed.
>>
>> -Akira
>>
>> On Sun, Feb 10, 2019 at 2:00 AM Masatake Iwasaki
>> <iw...@oss.nttdata.co.jp> wrote:
>>> Thanks for working on this, Akira.
>>>
>>> > The only usage I can see is Apache Slider, however, the
>>> > functionalities of Apache Slider have been merged into YARN.
>>>
>>> Do we have mailing lists other than yarn-dev to reach downstream
>> developers?
>>> It would be better to make it confident that old hamlet of Hadoop 3 is
>>> used nowhere.
>>>
>>> I'm +1 on making imcompatible change if this blocks another Java
>>> migration issues,
>>> while I don't see strong reason to hurry as I see the patch of YARN-9279.
>>>
>>> Masatake Iwasaki
>>>
>>> On 2/3/19 18:10, Akira Ajisaka wrote:
>>>> Filed https://issues.apache.org/jira/browse/YARN-9279 to remove the
>>>> old hamlet package.
>>>>
>>>> -Akira
>>>>
>>>> 2019年1月21日(月) 13:08 Akira Ajisaka <aa...@apache.org>:
>>>>> Hi folks,
>>>>>
>>>>> I'd like to remove the deprecated hamlet package to reduce the
>> maintenance cost.
>>>>> The old hamlet package has one character '_' and it is banned in Java
>>>>> 9+, so HADOOP-11875 deprecated this package and created a profile in
>>>>> pom.xml not to compile the package when the Java version is 9+. After
>>>>> the deprecation, we still have to maintenance the profile (see
>>>>> YARN-8123 and HADOOP-16046).
>>>>>
>>>>> The only usage I can see is Apache Slider, however, the
>>>>> functionalities of Apache Slider have been merged into YARN. Therefore
>>>>> I think there are no people using Slider with Hadoop 3.1+ and we can
>>>>> remove the package in 3.3+.
>>>>>
>>>>> Any thoughts?
>>>>>
>>>>> Regards,
>>>>> Akira
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: [DISCUSS] Removal of old hamlet package in 3.3+ or 3.4+
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
I'm basically +1 on removing the package.
The patch of YARN-9279 is still applicable to trunk.
If we are still unable to remove the package due to downstream projects,
another option could be always excluding the hamlet package from javadoc
build
as done in java9 profile only now?
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<excludePackageNames>org.apache.hadoop.yarn.webapp.hamlet</excludePackageNames>
</configuration>
</plugin>
On 2020/01/15 13:36, Akira Ajisaka wrote:
> Hi folks,
>
> Now I have a strong reason to remove the old hamlet package.
>
> There are 1000+ javadoc warnings in the package and they fill the output of
> the precommit javadoc module.
> That's why the new warnings and errors are ignored and sometimes they cause
> build errors.
>
> Now I'm investigating why the precommit job ignores new javadoc
> warnings/errors
> in https://issues.apache.org/jira/browse/HADOOP-16802. I'd like to remove
> the package to make the investigation easier.
>
> Regards,
> Akira
>
> On Thu, Feb 14, 2019 at 3:18 PM Akira Ajisaka <aa...@gmail.com> wrote:
>
>> Thanks Masatake for your comments.
>> Added the other Hadoop mailing lists to Cc.
>>
>>> I'm +1 on making imcompatible change if this blocks another Java
>> migration issues, while I don't see strong reason to hurry as I see the
>> patch of YARN-9279.
>> Agreed.
>>
>> -Akira
>>
>> On Sun, Feb 10, 2019 at 2:00 AM Masatake Iwasaki
>> <iw...@oss.nttdata.co.jp> wrote:
>>> Thanks for working on this, Akira.
>>>
>>> > The only usage I can see is Apache Slider, however, the
>>> > functionalities of Apache Slider have been merged into YARN.
>>>
>>> Do we have mailing lists other than yarn-dev to reach downstream
>> developers?
>>> It would be better to make it confident that old hamlet of Hadoop 3 is
>>> used nowhere.
>>>
>>> I'm +1 on making imcompatible change if this blocks another Java
>>> migration issues,
>>> while I don't see strong reason to hurry as I see the patch of YARN-9279.
>>>
>>> Masatake Iwasaki
>>>
>>> On 2/3/19 18:10, Akira Ajisaka wrote:
>>>> Filed https://issues.apache.org/jira/browse/YARN-9279 to remove the
>>>> old hamlet package.
>>>>
>>>> -Akira
>>>>
>>>> 2019年1月21日(月) 13:08 Akira Ajisaka <aa...@apache.org>:
>>>>> Hi folks,
>>>>>
>>>>> I'd like to remove the deprecated hamlet package to reduce the
>> maintenance cost.
>>>>> The old hamlet package has one character '_' and it is banned in Java
>>>>> 9+, so HADOOP-11875 deprecated this package and created a profile in
>>>>> pom.xml not to compile the package when the Java version is 9+. After
>>>>> the deprecation, we still have to maintenance the profile (see
>>>>> YARN-8123 and HADOOP-16046).
>>>>>
>>>>> The only usage I can see is Apache Slider, however, the
>>>>> functionalities of Apache Slider have been merged into YARN. Therefore
>>>>> I think there are no people using Slider with Hadoop 3.1+ and we can
>>>>> remove the package in 3.3+.
>>>>>
>>>>> Any thoughts?
>>>>>
>>>>> Regards,
>>>>> Akira
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: [DISCUSS] Removal of old hamlet package in 3.3+ or 3.4+
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
I'm basically +1 on removing the package.
The patch of YARN-9279 is still applicable to trunk.
If we are still unable to remove the package due to downstream projects,
another option could be always excluding the hamlet package from javadoc
build
as done in java9 profile only now?
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<excludePackageNames>org.apache.hadoop.yarn.webapp.hamlet</excludePackageNames>
</configuration>
</plugin>
On 2020/01/15 13:36, Akira Ajisaka wrote:
> Hi folks,
>
> Now I have a strong reason to remove the old hamlet package.
>
> There are 1000+ javadoc warnings in the package and they fill the output of
> the precommit javadoc module.
> That's why the new warnings and errors are ignored and sometimes they cause
> build errors.
>
> Now I'm investigating why the precommit job ignores new javadoc
> warnings/errors
> in https://issues.apache.org/jira/browse/HADOOP-16802. I'd like to remove
> the package to make the investigation easier.
>
> Regards,
> Akira
>
> On Thu, Feb 14, 2019 at 3:18 PM Akira Ajisaka <aa...@gmail.com> wrote:
>
>> Thanks Masatake for your comments.
>> Added the other Hadoop mailing lists to Cc.
>>
>>> I'm +1 on making imcompatible change if this blocks another Java
>> migration issues, while I don't see strong reason to hurry as I see the
>> patch of YARN-9279.
>> Agreed.
>>
>> -Akira
>>
>> On Sun, Feb 10, 2019 at 2:00 AM Masatake Iwasaki
>> <iw...@oss.nttdata.co.jp> wrote:
>>> Thanks for working on this, Akira.
>>>
>>> > The only usage I can see is Apache Slider, however, the
>>> > functionalities of Apache Slider have been merged into YARN.
>>>
>>> Do we have mailing lists other than yarn-dev to reach downstream
>> developers?
>>> It would be better to make it confident that old hamlet of Hadoop 3 is
>>> used nowhere.
>>>
>>> I'm +1 on making imcompatible change if this blocks another Java
>>> migration issues,
>>> while I don't see strong reason to hurry as I see the patch of YARN-9279.
>>>
>>> Masatake Iwasaki
>>>
>>> On 2/3/19 18:10, Akira Ajisaka wrote:
>>>> Filed https://issues.apache.org/jira/browse/YARN-9279 to remove the
>>>> old hamlet package.
>>>>
>>>> -Akira
>>>>
>>>> 2019年1月21日(月) 13:08 Akira Ajisaka <aa...@apache.org>:
>>>>> Hi folks,
>>>>>
>>>>> I'd like to remove the deprecated hamlet package to reduce the
>> maintenance cost.
>>>>> The old hamlet package has one character '_' and it is banned in Java
>>>>> 9+, so HADOOP-11875 deprecated this package and created a profile in
>>>>> pom.xml not to compile the package when the Java version is 9+. After
>>>>> the deprecation, we still have to maintenance the profile (see
>>>>> YARN-8123 and HADOOP-16046).
>>>>>
>>>>> The only usage I can see is Apache Slider, however, the
>>>>> functionalities of Apache Slider have been merged into YARN. Therefore
>>>>> I think there are no people using Slider with Hadoop 3.1+ and we can
>>>>> remove the package in 3.3+.
>>>>>
>>>>> Any thoughts?
>>>>>
>>>>> Regards,
>>>>> Akira
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: [DISCUSS] Removal of old hamlet package in 3.3+ or 3.4+
Posted by Masatake Iwasaki <iw...@oss.nttdata.co.jp>.
I'm basically +1 on removing the package.
The patch of YARN-9279 is still applicable to trunk.
If we are still unable to remove the package due to downstream projects,
another option could be always excluding the hamlet package from javadoc
build
as done in java9 profile only now?
<plugin>
<artifactId>maven-javadoc-plugin</artifactId>
<configuration>
<excludePackageNames>org.apache.hadoop.yarn.webapp.hamlet</excludePackageNames>
</configuration>
</plugin>
On 2020/01/15 13:36, Akira Ajisaka wrote:
> Hi folks,
>
> Now I have a strong reason to remove the old hamlet package.
>
> There are 1000+ javadoc warnings in the package and they fill the output of
> the precommit javadoc module.
> That's why the new warnings and errors are ignored and sometimes they cause
> build errors.
>
> Now I'm investigating why the precommit job ignores new javadoc
> warnings/errors
> in https://issues.apache.org/jira/browse/HADOOP-16802. I'd like to remove
> the package to make the investigation easier.
>
> Regards,
> Akira
>
> On Thu, Feb 14, 2019 at 3:18 PM Akira Ajisaka <aa...@gmail.com> wrote:
>
>> Thanks Masatake for your comments.
>> Added the other Hadoop mailing lists to Cc.
>>
>>> I'm +1 on making imcompatible change if this blocks another Java
>> migration issues, while I don't see strong reason to hurry as I see the
>> patch of YARN-9279.
>> Agreed.
>>
>> -Akira
>>
>> On Sun, Feb 10, 2019 at 2:00 AM Masatake Iwasaki
>> <iw...@oss.nttdata.co.jp> wrote:
>>> Thanks for working on this, Akira.
>>>
>>> > The only usage I can see is Apache Slider, however, the
>>> > functionalities of Apache Slider have been merged into YARN.
>>>
>>> Do we have mailing lists other than yarn-dev to reach downstream
>> developers?
>>> It would be better to make it confident that old hamlet of Hadoop 3 is
>>> used nowhere.
>>>
>>> I'm +1 on making imcompatible change if this blocks another Java
>>> migration issues,
>>> while I don't see strong reason to hurry as I see the patch of YARN-9279.
>>>
>>> Masatake Iwasaki
>>>
>>> On 2/3/19 18:10, Akira Ajisaka wrote:
>>>> Filed https://issues.apache.org/jira/browse/YARN-9279 to remove the
>>>> old hamlet package.
>>>>
>>>> -Akira
>>>>
>>>> 2019年1月21日(月) 13:08 Akira Ajisaka <aa...@apache.org>:
>>>>> Hi folks,
>>>>>
>>>>> I'd like to remove the deprecated hamlet package to reduce the
>> maintenance cost.
>>>>> The old hamlet package has one character '_' and it is banned in Java
>>>>> 9+, so HADOOP-11875 deprecated this package and created a profile in
>>>>> pom.xml not to compile the package when the Java version is 9+. After
>>>>> the deprecation, we still have to maintenance the profile (see
>>>>> YARN-8123 and HADOOP-16046).
>>>>>
>>>>> The only usage I can see is Apache Slider, however, the
>>>>> functionalities of Apache Slider have been merged into YARN. Therefore
>>>>> I think there are no people using Slider with Hadoop 3.1+ and we can
>>>>> remove the package in 3.3+.
>>>>>
>>>>> Any thoughts?
>>>>>
>>>>> Regards,
>>>>> Akira
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
>>> For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: [DISCUSS] Removal of old hamlet package in 3.3+ or 3.4+
Posted by Akira Ajisaka <aa...@gmail.com>.
Hi folks,
Now I have a strong reason to remove the old hamlet package.
There are 1000+ javadoc warnings in the package and they fill the output of
the precommit javadoc module.
That's why the new warnings and errors are ignored and sometimes they cause
build errors.
Now I'm investigating why the precommit job ignores new javadoc
warnings/errors
in https://issues.apache.org/jira/browse/HADOOP-16802. I'd like to remove
the package to make the investigation easier.
Regards,
Akira
On Thu, Feb 14, 2019 at 3:18 PM Akira Ajisaka <aa...@gmail.com> wrote:
> Thanks Masatake for your comments.
> Added the other Hadoop mailing lists to Cc.
>
> > I'm +1 on making imcompatible change if this blocks another Java
> migration issues, while I don't see strong reason to hurry as I see the
> patch of YARN-9279.
> Agreed.
>
> -Akira
>
> On Sun, Feb 10, 2019 at 2:00 AM Masatake Iwasaki
> <iw...@oss.nttdata.co.jp> wrote:
> >
> > Thanks for working on this, Akira.
> >
> > > The only usage I can see is Apache Slider, however, the
> > > functionalities of Apache Slider have been merged into YARN.
> >
> > Do we have mailing lists other than yarn-dev to reach downstream
> developers?
> > It would be better to make it confident that old hamlet of Hadoop 3 is
> > used nowhere.
> >
> > I'm +1 on making imcompatible change if this blocks another Java
> > migration issues,
> > while I don't see strong reason to hurry as I see the patch of YARN-9279.
> >
> > Masatake Iwasaki
> >
> > On 2/3/19 18:10, Akira Ajisaka wrote:
> > > Filed https://issues.apache.org/jira/browse/YARN-9279 to remove the
> > > old hamlet package.
> > >
> > > -Akira
> > >
> > > 2019年1月21日(月) 13:08 Akira Ajisaka <aa...@apache.org>:
> > >> Hi folks,
> > >>
> > >> I'd like to remove the deprecated hamlet package to reduce the
> maintenance cost.
> > >>
> > >> The old hamlet package has one character '_' and it is banned in Java
> > >> 9+, so HADOOP-11875 deprecated this package and created a profile in
> > >> pom.xml not to compile the package when the Java version is 9+. After
> > >> the deprecation, we still have to maintenance the profile (see
> > >> YARN-8123 and HADOOP-16046).
> > >>
> > >> The only usage I can see is Apache Slider, however, the
> > >> functionalities of Apache Slider have been merged into YARN. Therefore
> > >> I think there are no people using Slider with Hadoop 3.1+ and we can
> > >> remove the package in 3.3+.
> > >>
> > >> Any thoughts?
> > >>
> > >> Regards,
> > >> Akira
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
>
Re: [DISCUSS] Removal of old hamlet package in 3.3+ or 3.4+
Posted by Akira Ajisaka <aa...@gmail.com>.
Hi folks,
Now I have a strong reason to remove the old hamlet package.
There are 1000+ javadoc warnings in the package and they fill the output of
the precommit javadoc module.
That's why the new warnings and errors are ignored and sometimes they cause
build errors.
Now I'm investigating why the precommit job ignores new javadoc
warnings/errors
in https://issues.apache.org/jira/browse/HADOOP-16802. I'd like to remove
the package to make the investigation easier.
Regards,
Akira
On Thu, Feb 14, 2019 at 3:18 PM Akira Ajisaka <aa...@gmail.com> wrote:
> Thanks Masatake for your comments.
> Added the other Hadoop mailing lists to Cc.
>
> > I'm +1 on making imcompatible change if this blocks another Java
> migration issues, while I don't see strong reason to hurry as I see the
> patch of YARN-9279.
> Agreed.
>
> -Akira
>
> On Sun, Feb 10, 2019 at 2:00 AM Masatake Iwasaki
> <iw...@oss.nttdata.co.jp> wrote:
> >
> > Thanks for working on this, Akira.
> >
> > > The only usage I can see is Apache Slider, however, the
> > > functionalities of Apache Slider have been merged into YARN.
> >
> > Do we have mailing lists other than yarn-dev to reach downstream
> developers?
> > It would be better to make it confident that old hamlet of Hadoop 3 is
> > used nowhere.
> >
> > I'm +1 on making imcompatible change if this blocks another Java
> > migration issues,
> > while I don't see strong reason to hurry as I see the patch of YARN-9279.
> >
> > Masatake Iwasaki
> >
> > On 2/3/19 18:10, Akira Ajisaka wrote:
> > > Filed https://issues.apache.org/jira/browse/YARN-9279 to remove the
> > > old hamlet package.
> > >
> > > -Akira
> > >
> > > 2019年1月21日(月) 13:08 Akira Ajisaka <aa...@apache.org>:
> > >> Hi folks,
> > >>
> > >> I'd like to remove the deprecated hamlet package to reduce the
> maintenance cost.
> > >>
> > >> The old hamlet package has one character '_' and it is banned in Java
> > >> 9+, so HADOOP-11875 deprecated this package and created a profile in
> > >> pom.xml not to compile the package when the Java version is 9+. After
> > >> the deprecation, we still have to maintenance the profile (see
> > >> YARN-8123 and HADOOP-16046).
> > >>
> > >> The only usage I can see is Apache Slider, however, the
> > >> functionalities of Apache Slider have been merged into YARN. Therefore
> > >> I think there are no people using Slider with Hadoop 3.1+ and we can
> > >> remove the package in 3.3+.
> > >>
> > >> Any thoughts?
> > >>
> > >> Regards,
> > >> Akira
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
>
Re: [DISCUSS] Removal of old hamlet package in 3.3+ or 3.4+
Posted by Akira Ajisaka <aa...@gmail.com>.
Hi folks,
Now I have a strong reason to remove the old hamlet package.
There are 1000+ javadoc warnings in the package and they fill the output of
the precommit javadoc module.
That's why the new warnings and errors are ignored and sometimes they cause
build errors.
Now I'm investigating why the precommit job ignores new javadoc
warnings/errors
in https://issues.apache.org/jira/browse/HADOOP-16802. I'd like to remove
the package to make the investigation easier.
Regards,
Akira
On Thu, Feb 14, 2019 at 3:18 PM Akira Ajisaka <aa...@gmail.com> wrote:
> Thanks Masatake for your comments.
> Added the other Hadoop mailing lists to Cc.
>
> > I'm +1 on making imcompatible change if this blocks another Java
> migration issues, while I don't see strong reason to hurry as I see the
> patch of YARN-9279.
> Agreed.
>
> -Akira
>
> On Sun, Feb 10, 2019 at 2:00 AM Masatake Iwasaki
> <iw...@oss.nttdata.co.jp> wrote:
> >
> > Thanks for working on this, Akira.
> >
> > > The only usage I can see is Apache Slider, however, the
> > > functionalities of Apache Slider have been merged into YARN.
> >
> > Do we have mailing lists other than yarn-dev to reach downstream
> developers?
> > It would be better to make it confident that old hamlet of Hadoop 3 is
> > used nowhere.
> >
> > I'm +1 on making imcompatible change if this blocks another Java
> > migration issues,
> > while I don't see strong reason to hurry as I see the patch of YARN-9279.
> >
> > Masatake Iwasaki
> >
> > On 2/3/19 18:10, Akira Ajisaka wrote:
> > > Filed https://issues.apache.org/jira/browse/YARN-9279 to remove the
> > > old hamlet package.
> > >
> > > -Akira
> > >
> > > 2019年1月21日(月) 13:08 Akira Ajisaka <aa...@apache.org>:
> > >> Hi folks,
> > >>
> > >> I'd like to remove the deprecated hamlet package to reduce the
> maintenance cost.
> > >>
> > >> The old hamlet package has one character '_' and it is banned in Java
> > >> 9+, so HADOOP-11875 deprecated this package and created a profile in
> > >> pom.xml not to compile the package when the Java version is 9+. After
> > >> the deprecation, we still have to maintenance the profile (see
> > >> YARN-8123 and HADOOP-16046).
> > >>
> > >> The only usage I can see is Apache Slider, however, the
> > >> functionalities of Apache Slider have been merged into YARN. Therefore
> > >> I think there are no people using Slider with Hadoop 3.1+ and we can
> > >> remove the package in 3.3+.
> > >>
> > >> Any thoughts?
> > >>
> > >> Regards,
> > >> Akira
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
>
Re: [DISCUSS] Removal of old hamlet package in 3.3+ or 3.4+
Posted by Akira Ajisaka <aa...@gmail.com>.
Hi folks,
Now I have a strong reason to remove the old hamlet package.
There are 1000+ javadoc warnings in the package and they fill the output of
the precommit javadoc module.
That's why the new warnings and errors are ignored and sometimes they cause
build errors.
Now I'm investigating why the precommit job ignores new javadoc
warnings/errors
in https://issues.apache.org/jira/browse/HADOOP-16802. I'd like to remove
the package to make the investigation easier.
Regards,
Akira
On Thu, Feb 14, 2019 at 3:18 PM Akira Ajisaka <aa...@gmail.com> wrote:
> Thanks Masatake for your comments.
> Added the other Hadoop mailing lists to Cc.
>
> > I'm +1 on making imcompatible change if this blocks another Java
> migration issues, while I don't see strong reason to hurry as I see the
> patch of YARN-9279.
> Agreed.
>
> -Akira
>
> On Sun, Feb 10, 2019 at 2:00 AM Masatake Iwasaki
> <iw...@oss.nttdata.co.jp> wrote:
> >
> > Thanks for working on this, Akira.
> >
> > > The only usage I can see is Apache Slider, however, the
> > > functionalities of Apache Slider have been merged into YARN.
> >
> > Do we have mailing lists other than yarn-dev to reach downstream
> developers?
> > It would be better to make it confident that old hamlet of Hadoop 3 is
> > used nowhere.
> >
> > I'm +1 on making imcompatible change if this blocks another Java
> > migration issues,
> > while I don't see strong reason to hurry as I see the patch of YARN-9279.
> >
> > Masatake Iwasaki
> >
> > On 2/3/19 18:10, Akira Ajisaka wrote:
> > > Filed https://issues.apache.org/jira/browse/YARN-9279 to remove the
> > > old hamlet package.
> > >
> > > -Akira
> > >
> > > 2019年1月21日(月) 13:08 Akira Ajisaka <aa...@apache.org>:
> > >> Hi folks,
> > >>
> > >> I'd like to remove the deprecated hamlet package to reduce the
> maintenance cost.
> > >>
> > >> The old hamlet package has one character '_' and it is banned in Java
> > >> 9+, so HADOOP-11875 deprecated this package and created a profile in
> > >> pom.xml not to compile the package when the Java version is 9+. After
> > >> the deprecation, we still have to maintenance the profile (see
> > >> YARN-8123 and HADOOP-16046).
> > >>
> > >> The only usage I can see is Apache Slider, however, the
> > >> functionalities of Apache Slider have been merged into YARN. Therefore
> > >> I think there are no people using Slider with Hadoop 3.1+ and we can
> > >> remove the package in 3.3+.
> > >>
> > >> Any thoughts?
> > >>
> > >> Regards,
> > >> Akira
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
> >
>