+1 . Thanks Wangda.
- Sunil
On Sat, Feb 2, 2019 at 3:54 AM Wangda Tan wrote:
> Hi all,
>
> According to positive feedbacks from the thread [1]
>
> This is vote thread to start a new subproject named "hadoop-submarine"
> which follows the release process already established for ozone.
>
> The
+1
On Sat, 2 Feb 2019, 09:51 Rohith Sharma K S +1
>
> On Sat, Feb 2, 2019, 3:54 AM Wangda Tan wrote:
>
> > Hi all,
> >
> > According to positive feedbacks from the thread [1]
> >
> > This is vote thread to start a new subproject named "hadoop-submarine"
> > which follows the release process
+1
On Sat, Feb 2, 2019, 3:54 AM Wangda Tan wrote:
> Hi all,
>
> According to positive feedbacks from the thread [1]
>
> This is vote thread to start a new subproject named "hadoop-submarine"
> which follows the release process already established for ozone.
>
> The vote runs for usual 7 days,
Just to make sure we are on the same page, as the subject of this thread is
too generic and confusing.
*The proposal is to move branch-2 Jenkins builds such as precommit to run
tests on openJDK-8.*
We do not want to break Java 7 source compatibility. The sources and
releases will still depend on
+1
Thanks,
Bharat
On 2/1/19, 3:12 PM, "Anu Engineer" wrote:
+1
--Anu
On 2/1/19, 3:02 PM, "Jonathan Hung" wrote:
+1. Thanks Wangda.
Jonathan Hung
On Fri, Feb 1, 2019 at 2:25 PM Dinesh Chitlangia <
+1
--Anu
On 2/1/19, 3:02 PM, "Jonathan Hung" wrote:
+1. Thanks Wangda.
Jonathan Hung
On Fri, Feb 1, 2019 at 2:25 PM Dinesh Chitlangia <
dchitlan...@hortonworks.com> wrote:
> +1 (non binding), thanks Wangda for organizing this.
>
> Regards,
>
+1. Thanks Wangda.
Jonathan Hung
On Fri, Feb 1, 2019 at 2:25 PM Dinesh Chitlangia <
dchitlan...@hortonworks.com> wrote:
> +1 (non binding), thanks Wangda for organizing this.
>
> Regards,
> Dinesh
>
>
>
> On 2/1/19, 5:24 PM, "Wangda Tan" wrote:
>
> Hi all,
>
> According to positive
Hi all,
According to positive feedbacks from the thread [1]
This is vote thread to start a new subproject named "hadoop-submarine"
which follows the release process already established for ozone.
The vote runs for usual 7 days, which ends at Feb 8th 5 PM PDT.
Thanks,
Wangda Tan
[1]
If HDFS or YARN breaks compatibility with Submarine, it will require to make
release to catch up with the latest Hadoop changes. On hadoop.apache.org
website, the latest news may always have Submarine on top to repair
compatibility with latest of Hadoop. This may overwhelm any interesting
Eric,
Thanks for your reconsideration. We will definitely try best to not break
compatibilities, etc. like how we did to other components!
Really appreciate everybody's support, thoughts, suggestions shared on this
thread. Given the discussion went very positive, I will go ahead to send a
voting
+1.
I like the idea.
For me, submarine/ML-job-execution seems to be a natural extension of
the existing Hadoop/Yarn capabilities.
And like the proposed project structure / release lifecycle, too. I
think it's better to be more modularized but keep the development in the
same project. IMHO it
This is a great proposal. +1.
Thanks,
Hanisha
On 2/1/19, 11:04 AM, "Bharat Viswanadham" wrote:
>Thank You Wangda for driving this discussion.
>+1 for a separate release for submarine.
>Having own release cadence will help iterate the project to grow at a faster
>pace and also get the
Thanks Vinod and Steve, agreed about java7 compile compatibility. At least
for now, we should be able to maintain java7 source compatibility and run
tests on java8. There's a test run here:
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86-jhung/46/
which calls a java8 specific API,
Thank You Wangda for driving this discussion.
+1 for a separate release for submarine.
Having own release cadence will help iterate the project to grow at a faster
pace and also get the new features in hand to the users, and get their feedback
quickly.
Thanks,
Bharat
On 2/1/19, 10:54 AM,
+1, thanks for bringing this up, Wangda. This will help expanding the Hadoop
ecosystem by supporting new AI/ML workloads.
Thanks,
Xiaoyu
On 2/1/19, 10:58 AM, "Dinesh Chitlangia" wrote:
+1 This is a fantastic recommendation given the increasing interest in ML
across the globe.
+1, Thanks for driving this. With rise of use cases running ML along with
traditional applications this will be of great help.
Thanks,
Ajay
On 2/1/19, 10:49 AM, "Suma Shivaprasad" wrote:
+1. Thanks for bringing this up Wangda.
Makes sense to have Submarine follow its own
Thanks everyone for sharing thoughts!
Eric, appreciate your suggestions. But there are many examples to have
separate releases, like Hive's storage API, OZone, etc. For loosely coupled
sub-projects, it gonna be great (at least for most of the users) to have
separate releases so new features can
+1. Thanks for bringing this up Wangda.
Makes sense to have Submarine follow its own release cadence given the good
momentum/adoption so far. Also, making it run with older versions of Hadoop
would drive higher adoption.
Suma
On Fri, Feb 1, 2019 at 9:40 AM Eric Yang wrote:
> Submarine is an
+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
Submarine is an application built for YARN framework, but it does not have
strong dependency on YARN development. For this kind of projects, it would be
best to enter Apache Incubator cycles to create a new community. Apache
commons is the only project other than Incubator that has
+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 the progress made in Submarine last year, the
> community grows fast and quiet collaborative. I
21 matches
Mail list logo
