Dmitri Chmelev created HADOOP-16090:
---
Summary: deleteUnnecessaryFakeDirectories() creates unnecessary
delete markers in a versioned S3 bucket
Key: HADOOP-16090
URL: https://issues.apache.org/jira/browse/HADOOP-1
+1, It is very necessary to use Submarine on older Hadoop. What's more, the
development of deep learning is too fast, and Submarine must keep faster
release iterate .
> 在 2019年2月1日，上午2:53，Wangda Tan 写道：
>
> Hi devs,
>
> Since we started submarine-related effort last year, we received a
+1 from me on this.
ML/DL is one of the fast growing areas and a runtime on YARN helps customers
to have ML/DL workloads to run on same cluster where the ETL or other
traditional
big data workloads ingest or mine data.
Faster release cadence can pace up the development for Submarine and more
agile
+1, Few interested ML/DL folks from Banglore asked about Submarine release
for trying out TensorFlow on YARN. We told them wait for release since they
were not ready to use trunk. I see agile release cycle for Submarine brings
lot of added value.
-Rohith Sharma K S
On Fri, 1 Feb 2019 at 00:34, Wa
+ Hadoop Common & Jira Link
https://issues.apache.org/jira/browse/HADOOP-15891
Thanks
Zhenzhao Wang 于2019年1月31日周四 下午4:05写道：
> Hi folks,
> I developed a feature to provide regex based mount points in
> viewfilesystem/viewfs. It empowers us to adopt rule based mount points and
> had been running w
Thanks for bringing this up Wangda. +1
Makes a lot of sense to have Submarine follow its own release cadence - for
all the reasons you outlined.
I would one up this proposal to ask why shouldn't we allow YARN to have its
own releases as well - but that is for a separate thread :)
Cheers
-Arun
On
>> I propose to adopt Ozone model: which is the same master branch, different
>> release cycle, and different release branch. It is a great example to show
>> agile release we can do (2 Ozone releases after Oct 2018) with less
>> overhead to setup CI, projects, etc.
I second this, especially this
+1. This is important for improving the deep learning on hadoop story.
There's recently a lot of momentum for this, and decoupling
submarine/hadoop will help it continue.
Jonathan Hung
On Thu, Jan 31, 2019 at 11:04 AM Wangda Tan wrote:
> Hi devs,
>
> Since we started submarine-related effort l
Hi devs,
Since we started submarine-related effort last year, we received a lot of
feedbacks, several companies (such as Netease, China Mobile, etc.) are
trying to deploy Submarine to their Hadoop cluster along with big data
workloads. Linkedin also has big interests to contribute a Submarine Ton
1, 3. There are 38 Apache projects hosting docker images on Docker hub using
Apache Organization. By browsing Apache github mirror. There are only 7
projects using a separate repository for docker image build. Popular projects
official images are not from Apache organization, such as zookeepe
Hi Eric,
Thanks for the answers
1.
> Hadoop-docker-ozone.git source tree naming seems to create a unique
process for Ozone.
Not at all. We would like to follow the existing practice which is
established in HADOOP-14898. In HDDS-851 we discussed why we need two
separated repositories for hadoo
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1033/
[Jan 30, 2019 2:29:56 AM] (aajisaka) HADOOP-14178. Move Mockito up to version
2.23.4. Contributed by Akira
[Jan 30, 2019 5:56:28 AM] (yqlin) HDDS-1024. Handle DeleteContainerCommand in
the
[Jan 30, 2019 1
12 matches
Mail list logo
