n Thu, May 20, 2021 at 6:36 AM Sean Busbey
> > > > > > >> mailto:sbus...@apple.com.invalid
> > >
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >> Hello!
> > > > > > >>
> > > > > > >> What do folks think about changing our line
> length
> > > > > > >> guidelines to allow
> > > > > > >> for 100 character width?
> > > > > > >>
> > > > > > >> Currently, we tell folks to follow the sun style
> > > guide
> > > > > > with
> > > > > > >> some
> > > > > > >> exception unrelated to line length. That guide says width
> > of
> > > 80
> > > > > is
> > > > > > the
> > > > > > >> standard and our current check style rules act as
> > > enforcement.
> > > > > > >>
> > > > > > >> Looking at the current trunk codebase our
> nightly
> > > > build
> > > > > > >> shows a total
> > > > > > >> of ~15k line length violations; it’s about 18% of
> > identified
> > > > > > >> checkstyle
> > > > > > >> issues.
> > > > > > >>
> > > > > > >> The vast majority of those line length
> violations
> > > are
> > > > <=
> > > > > > 100
> > > > > > >> characters
> > > > > > >> long. 100 characters happens to be the length for the
> > Google
> > > > Java
> > > > > > >> Style
> > > > > > >> Guide, another commonly adopted style guide for java
> > > projects,
> > > > > so I
> > > > > > >> suspect
> > > > > > >> these longer lines leaking past the checkstyle precommit
> > > > warning
> > > > > > >> might be a
> > > > > > >> reflection of committers working across multiple java
> > > > codebases.
> > > > > > >>
> > > > > > >> I don’t feel strongly about lines being longer,
> > but
> > > I
> > > > > > would
> > > > > > >> like to
> > > > > > >> move towards more consistent style enforcement as a
> > project.
> > > > > > Updating
> > > > > > >> our
> > > > > > >> project guidance to allow for 100 character lines would
> > > reduce
> > > > > the
> > > > > > >> likelihood that folks bringing in new contributions need
> a
> > > > > > precommit
> > > > > > >> test
> > > > > > >> cycle to get the formatting correct.
> > > > > > >>
> > > > > > >> Does anyone feel strongly about keeping the line
> > > > length
> > > > > > >> limit at 80
> > > > > > >> characters?
> > > > > > >>
> > > > > > >> Does anyone feel strongly about contributions
> > coming
> > > > in
> > > > > > that
> > > > > > >> clear up
> > > > > > >> line length violations?
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > -
> > > > > > >> To unsubscribe, e-mail:
> > > > > > >> common-dev-unsubscr...@hadoop.apache.org > > > > > common-dev-unsubscr...@hadoop.apache.org>
> > > > > > >> For additional commands, e-mail:
> > > > > > >> common-dev-h...@hadoop.apache.org > > > > > common-dev-h...@hadoop.apache.org>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > -
> > > > > > >> To unsubscribe, e-mail:
> > > > > > common-dev-unsubscr...@hadoop.apache.org > > > > > common-dev-unsubscr...@hadoop.apache.org>
> > > > > > >> For additional commands, e-mail:
> > > > > > >> common-dev-h...@hadoop.apache.org > > > > > common-dev-h...@hadoop.apache.org>
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > >
> > -
> > > > > > >> To unsubscribe, e-mail:
> > > > common-dev-unsubscr...@hadoop.apache.org
> > > > > > <mailto:common-dev-unsubscr...@hadoop.apache.org>
> > > > > > >> For additional commands, e-mail:
> > > > > common-dev-h...@hadoop.apache.org
> > > > > > <mailto:common-dev-h...@hadoop.apache.org>
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
--
John Zhuge
; >>>> On Mon, Mar 2, 2020 at 6:30 PM Sree Vaddi
> >> >>>> wrote:
> >> >>>>
> >> >>>>> +1
> >> >>>>>
> >> >>>>> Sent from Yahoo Mail on Android
> >> >>>>>
> >> >>>>> On Mon, Mar 2, 2020 at 5:12 PM, Wei-Chiu Chuang<
> weic...@apache.org>
> >> >>>>> wrote: Hi,
> >> >>>>>
> >> >>>>> Following the discussion to end branch-2.8, I want to start a
> >> >>>>> discussion
> >> >>>>> around what's next with branch-2.9. I am hesitant to use the word
> "end
> >> >>>>> of
> >> >>>>> life" but consider these facts:
> >> >>>>>
> >> >>>>> * 2.9.0 was released Dec 17, 2017.
> >> >>>>> * 2.9.2, the last 2.9.x release, went out Nov 19 2018, which is
> more
> >> >>>>> than
> >> >>>>> 15 months ago.
> >> >>>>> * no one seems to be interested in being the release manager for
> 2.9.3.
> >> >>>>> * Most if not all of the active Hadoop contributors are using
> Hadoop
> >> >>>>> 2.10
> >> >>>>> or Hadoop 3.x.
> >> >>>>> * We as a community do not have the cycle to manage multiple
> release
> >> >>>>> line,
> >> >>>>> especially since Hadoop 3.3.0 is coming out soon.
> >> >>>>>
> >> >>>>> It is perhaps the time to gradually reduce our footprint in Hadoop
> >> >>>>> 2.x, and
> >> >>>>> encourage people to upgrade to Hadoop 3.x
> >> >>>>>
> >> >>>>> Thoughts?
> >> >>>>>
> >> >>>>>
>
--
John Zhuge
;> Thanks Wei-Chiu for starting the discussion,
> > > >>>>>>
> > > >>>>>> +1 for the EoL.
> > > >>>>>>
> > > >>>>>> -Akira
> > > >>>>>>
> > > >>>>>> On Tue, Feb 18, 2020 at 4:59 PM Ayush Saxena <
> ayush...@gmail.com>
> > > >>>> wrote:
> > > >>>>>>
> > > >>>>>>> Thanx Wei-Chiu for initiating this
> > > >>>>>>> +1 for marking 2.8 EOL
> > > >>>>>>>
> > > >>>>>>> -Ayush
> > > >>>>>>>
> > > >>>>>>>> On 17-Feb-2020, at 11:14 PM, Wei-Chiu Chuang <
> > > >>> weic...@apache.org>
> > > >>>>>> wrote:
> > > >>>>>>>>
> > > >>>>>>>> The last Hadoop 2.8.x release, 2.8.5, was GA on September
> 15th
> > > >>>> 2018.
> > > >>>>>>>>
> > > >>>>>>>> It's been 17 months since the release and the community by and
> > > >>>> large
> > > >>>>>> have
> > > >>>>>>>> moved up to 2.9/2.10/3.x.
> > > >>>>>>>>
> > > >>>>>>>> With Hadoop 3.3.0 over the horizon, is it time to start the
> EOL
> > > >>>>>>> discussion
> > > >>>>>>>> and reduce the number of active branches?
> > > >>>>>>>
> > > >>>>>>>
> > > >>>
> -
> > > >>>>>>> To unsubscribe, e-mail:
> common-dev-unsubscr...@hadoop.apache.org
> > > >>>>>>> For additional commands, e-mail:
> > > >>> common-dev-h...@hadoop.apache.org
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>
> > > >>>>>
> > > >>>>
> > > >>>
> > > >>
> > >
> > > Wilfred Spiegelenburg
> > > Staff Software Engineer
> > > <https://www.cloudera.com/>
> > >
> >
>
--
John Zhuge
ontributions to the
> > >> project.
> > >>
> > >> Please join me in congratulating him.
> > >>
> > >> Hearty Congratulations & Welcome aboard Stephen!
> > >>
> > >> Wei-Chiu Chuang
> > >> (On behalf of the Hadoop PMC)
> > >>
> >
> > -
> > To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org
> > For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org
> >
> >
>
--
John Zhuge
+1
Does Submarine support Jupyter?
On Fri, Feb 1, 2019 at 8:54 AM Zhe Zhang wrote:
> +1 on the proposal and looking forward to the progress of the project!
>
> On Thu, Jan 31, 2019 at 10:51 PM Weiwei Yang wrote:
>
> > Thanks for proposing this Wangda, my +1 as well.
> > It is amazing to see
+1 Like the new site.
On Sun, Sep 2, 2018 at 7:02 PM Weiwei Yang wrote:
> That's really nice, +1.
>
> --
> Weiwei
>
> On Sat, Sep 1, 2018 at 4:36 AM Wangda Tan wrote:
>
> > +1, thanks for working on this, Marton!
> >
> > Best,
> > Wangda
> >
> > On Fri, Aug 31, 2018 at 11:24 AM Arpit Agarwal
Thanks Xongjun for the excellent work to drive this release!
+1 (binding)
- Verified checksums and signatures of tarballs
- Built source with native, Oracle Java 1.8.0_152 on Mac OS X 10.13.5
- Verified cloud connectors:
- ADLS integration tests passed with 1 failure, not a
Thanks Andrew for the great effort! Here is my late vote.
+1 (binding)
- Verified checksums and signatures of tarballs
- Built source with native, Oracle Java 1.8.0_152 on Mac OS X 10.13.2
- Verified cloud connectors:
- S3A integration tests (perf tests skipped)
- Deployed
Oops, the vote was meant for 2.7.5. Sorry for the confusion.
My 2.8.3 vote coming up shortly.
On Tue, Dec 12, 2017 at 4:28 PM, John Zhuge <john.zh...@gmail.com> wrote:
> Thanks Junping for the great effort!
>
>
>- Verified checksums and signatures of all tarballs
&
Thanks Konstantin for the great effort!
+1 (binding)
- Verified checksums and signatures of all tarballs
- Built source with native, Azul Java 1.7.0_161 on Mac OS X 10.13.2
- Verified cloud connectors:
- All S3A integration tests
- Deployed both binary and built source to a
Thanks Junping for the great effort!
- Verified checksums and signatures of all tarballs
- Built source with native, Azul Java 1.7.0_161 on Mac OS X 10.13.2
- Verified cloud connectors:
- All S3A integration tests
- Deployed both binary and built source to a pseudo cluster,
+1 (binding)
- Verified checksums of all tarballs
- Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
- Passed all S3A and ADL integration tests
- Deployed both binary and built source to a pseudo cluster, passed the
following sanity tests in insecure, SSL, and
+1 (binding)
- Verified checksums and signatures of all tarballs
- Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
- Verified these cloud connectors:
- All S3A integration tests
- All ADL live unit tests
- Deployed both binary and built source to a pseudo
+1 (binding)
- Verified checksums and signatures of all tarballs
- Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
- Verified cloud connectors:
- All S3A integration tests
- All ADL live unit tests
- Deployed both binary and built source to a pseudo
+1 (binding)
- Verified checksums and signatures of all tarballs
- Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
- Verified cloud connectors:
- All S3A integration tests
- All ADL live unit tests
- Deployed both binary and built source to a pseudo
; Thanks,
> --Konstantin
>
> On Sun, Jul 30, 2017 at 11:24 PM, John Zhuge <john.zh...@gmail.com> wrote:
>
>> Hi Konstantin,
>>
>> Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
>>
>> +1 (non-binding)
>>
>>- Verified chec
Hi Konstantin,
Thanks a lot for the effort to prepare the 2.7.4-RC0 release!
+1 (non-binding)
- Verified checksums and signatures of all tarballs
- Built source with native, Java 1.8.0_131-b11 on Mac OS X 10.12.6
- Verified cloud connectors:
- All S3A integration tests
-
+1 (non-binding)
- Verified checksums and signatures of the tarballs
- Built source with native, Java 1.8.0_131 on Mac OS X 10.12.5
- Cloud connectors:
- A few S3A integration tests
- A few ADL live unit tests
- Deployed both binary and built source to a pseudo cluster,
False alarm, fixed the build issue with "mvn -U clean install".
On Wed, Jul 5, 2017 at 6:08 PM, John Zhuge <john.zh...@gmail.com> wrote:
> For some reason, I can't build the source.
>
> Got this when running "mvn install -U" inside directory
> &quo
For some reason, I can't build the source.
Got this when running "mvn install -U" inside directory
"hadoop-maven-plugins":
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
(default) on project hadoop-maven-plugins: Execution default of goal
- balancer start/stop
Needs the following JIRAs to pass all ADL tests:
- HADOOP-14205. No FileSystem for scheme: adl. Contributed by John Zhuge.
- HDFS-11132. Allow AccessControlException in contract tests when
getFileStatus on subdirectory of existing files. Contributed by Vishwajeet
21 matches
Mail list logo
