+1 (non-binding)
* built from the source tarball (archlinux) / verified signature
* Deployed to a kubernetes cluster (10/10 datanode/nodemanager pods)
* Enabled ec on hdfs directory (hdfs cli)
* Started example yarn jobs (pi/terragen)
* checked yarn ui/ui2
Thanks for all the efforts.
On 10/21/2017 02:41 AM, larry mccay wrote:
"We might want to start a security section for Hadoop wiki for each of the
services and components.
This helps to track what has been completed."
Do you mean to keep the audit checklist for each service and component
there?
Interesting idea, I
Hi,
I would like to bump this thread up.
TLDR; There is a proposed version of a new hadoop site which is
available from here: https://elek.github.io/hadoop-site-proposal/ and
https://issues.apache.org/jira/browse/HADOOP-14163
Please let me know what you think about it.
Longer version:
.
- We then modify the existing web-site to say that there is a new
site/experience that folks can click on a link and navigate to
- As this new website matures and gets feedback & fixes, we finally pull the
plug at a later point of time when we think we are good to go.
Thoughts?
+Vinod
On Feb 16
+1 (non-binding)
1. Built from the source package.
2. Checked the signature
3. Started docker based pseudo cluster and smoketested some basic
functionality (hdfs cli, ec cli, viewfs, yarn examples, spark word count
job)
Thank you very much the work Wangda.
Marton
On 08/02/2018 08:43 PM,
Hi All,
I would like to discuss creating an Alpha release for Ozone. The core
functionality of Ozone is complete but there are two missing features;
Security and HA, work on these features are progressing in Branches
HDDS-4 and HDDS-151. Right now, Ozone can handle millions of keys and
has a
very soon.
Thanks,
Marton
ps:
Please give me write permission to the OLD wiki
(https://wiki.apache.org/hadoop/), if you can. My username is MartonElek
Thanks a lot.
On 08/31/2018 10:07 AM, Elek, Marton wrote:
Bumping this thread at last time.
I have the following proposal:
1. I will request
with this plan. Please comment if you have objections.
Again: it allows immediate fallback at any time as svn repo will be kept
as is (+ I will keep it up-to-date in the next 2 months)
Thanks,
Marton
On 06/21/2018 09:00 PM, Elek, Marton wrote:
Thank you very much to bump up this thread
+1 (non binding)
I did a full build from source code, created a docker container and did
various basic level tests with robotframework based automation and
docker-compose based pseudo clusters[1].
Including:
* Hdfs federation smoke test
* Basic ViewFS configuration
* Yarn example jobs
*
Hi all,
Since the previous 0.2.1-alpha ozone release more than 170 patches have
been committed to the apache trunk under hadoop-ozone/hadoop-hdds
subprojects.
The 0.3.0-alpha release carries an S3 compatible rest server. This
allows S3 applications to work against Ozone with zero-changes. The
Hi all,
I've created the first release candidate (RC0) for Apache Hadoop Ozone
0.3.0-alpha according to the plans shared here previously.
This is the second release of Apache Hadoop Ozone. Notable changes since
the first release:
* A new S3 compatible rest server is added. Ozone can be used
Unfortunately a memory issue is found with the default settings. Fixed
in HDDS-834 (thanks Mukul and Shashikant)
I cancel this vote and start a rc1 soon.
Marton
On 11/13/18 1:53 PM, Elek, Marton wrote:
> Hi all,
>
> I've created the first release candidate (RC0) for Apache Hadoop Ozon
Hi all,
I've created the second release candidate (RC1) for Apache Hadoop Ozone
0.3.0-alpha including one more fix on top of the previous RC0 (HDDS-854)
This is the second release of Apache Hadoop Ozone. Notable changes since
the first release:
* A new S3 compatible rest server is added. Ozone
It gives me great pleasure to announce that the Apache Hadoop community
has voted to release Apache Hadoop Ozone 0.2.1-alpha.
Apache Hadoop Ozone is an object store for Hadoop built using Hadoop
Distributed Data Store.
For more information and to download, please check
Hi all,
After the recent discussion about the first Ozone release I've created
the first release candidate (RC0) for Apache Hadoop Ozone 0.2.1-alpha.
This release is alpha quality: it’s not recommended to use in production
but we believe that it’s stable enough to try it out the feature set
repository is correct for clone?
I can clone readable repository (https://github.com/apache/hadoop-site)
successfully though but cannot push back changes which is expected.
Thanks,
Junping
Elek, Marton mailto:e...@apache.org>>于2018年9月17日
周一上午6:15写道：
Hi Junping,
Thank you t
Thank you very much the tests and the votes for all of you.
The vote is PASSED with the following details:
3 binding +1, (thanks Anu, Xiaoyu, Arpit)
10 non-binding +1, (thanks Hanisha, Bharat, Shashikant, Sandeep, Lokesh,
Nanda, Mukul, Ajay, Dinesh) together with my closing +1 [*]
no -1/0
refreshed. It seems like to need
some manually steps to refresh the website -if so, can you also update to
the wiki?
Thanks,
Junping
Elek, Marton 于2018年9月20日 周四下午1:40写道：
> Please try
>
> git clone https://gitbox.apache.org/repos/
he pgp pool? That's what Nexus is validating
>> against. It might take time to propagate if you just pushed it.
>>
>> On Mon, Jan 14, 2019 at 9:59 AM Elek, Marton wrote:
>>
>>> Seems to be an INFRA issue for me:
>>>
>>> 1. I downloaded a sam
Thanks Sunil to manage this release.
+1 (non-binding)
1. built from the source (with clean local maven repo)
2. verified signatures + checksum
3. deployed 3 node cluster to Google Kubernetes Engine with generated
k8s resources [1]
4. Executed basic HDFS commands
5. Executed basic yarn example
Seems to be an INFRA issue for me:
1. I downloaded a sample jar file [1] + the signature from the
repository and it was ok, locally I verified it.
2. I tested it with an other Apache project (Ratis) and my key. I got
the same problem even if it worked at last year during the 0.3.0
release. (I
On 12/12/18 12:27 PM, Akira Ajisaka wrote:
> Thank you for your positive feedback! I'll file a jira to INFRA in this
> weekend.
>
>> If I understood well the only bigger task here is to update all the jenkins
>> jobs. (I am happy to help/contribute what I can do)
> Thank you Elek for the
Thanks Akira,
+1 (non-binding)
I think it's better to do it now at a planned date.
If I understood well the only bigger task here is to update all the
jenkins jobs. (I am happy to help/contribute what I can do)
Marton
On 12/8/18 6:25 AM, Akira Ajisaka wrote:
> Hi all,
>
> Apache Hadoop
It gives me great pleasure to announce that the Apache Hadoop community
has voted to release Apache Hadoop Ozone 0.3.0-alpha (Arches).
Apache Hadoop Ozone is an object store for Hadoop built using Hadoop
Distributed Data Store.
This release contains a new S3 compatible interface and additional
Thank you very much the tests and the votes for all of you.
The vote is PASSED with the following details:
3 binding +1, (thanks Arpit, Anu, Jitendra)
6 non-binding +1, (thanks Dinesh, Shashikant, Lokesh, Mukul, Bharat)
together with my closing +1 [*]
no -1/0
Thanks again, will publish the
t;
>
>> On 7 Jan 2019, at 06:55, Akira Ajisaka > <mailto:aajis...@apache.org>> wrote:
>>
>> Thanks Ayush for the report and thanks Elek for the fix!
>>
>> -Akira
>>
>> 2019年1月3日(木) 0:54 Elek, Marton > <mailto:e...@apache.org>>:
>
ack is welcome,
Thanks,
Marton
On 10/5/18 5:51 PM, Elek, Marton wrote:
>
> Hi everybody,
>
>
> We start a new community call series about Apache Hadoop Ozone. It's an
> informal discussion about the current items, short-term plans,
> directions and contribution possibilities.
of the git.apache.org. It seems to be a mirror
page only for the old-style+svn repositories))
On 1/7/19 3:18 PM, Steve Loughran wrote:
> OK. so the original git://git.apache.org/hadoop.git is in fact deceased?
>
>
> On 7 Jan 2019, at 14:15, Elek, Marton
> mailto:e...@apache.org>&g
Thanks the report Ayush,
The bogus repository is removed by the INFRA:
https://issues.apache.org/jira/browse/INFRA-17526
And the cwiki page[1] is updated to use the gitbox url instead of
git.apache.org
Marton
[1] https://cwiki.apache.org/confluence/display/HADOOP/Git+And+Hadoop
On 1/2/19
Thank you Eric to describe the problem.
I have multiple small comments, trying to separate them.
I. separated vs in-build container image creation
> The disadvantages are:
>
> 1. Require developer to have access to docker.
> 2. Default build takes longer.
These are not the only
> If versioning is done correctly, older branches can have the same docker
> subproject, and Hadoop 2.7.8 can be released for older Hadoop branches. We
> don't generate timeline paradox to allow changing the history of Hadoop
> 2.7.1. That release has passed and let it stay that way.
I
release is ok to have wriggle room for developers, but I don't think that
> flexibility is necessary for official release.
>
> Regards,
> Eric
>
> On 3/21/19, 2:44 PM, "Elek, Marton" wrote:
>
>
>
> > If versioning is done correctly, older branches
YARN-7129 style of build process, and see this is a possible solution to
> solve docker image generation issue? Thanks
>
> Regards,
> Eric
>
> On 1/29/19, 3:44 PM, "Arpit Agarwal"
> wrote:
>
> I’ve request
+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
> dockerfile-maven-plugin approach.
>
> Regards,
> Eric
>
> On 1/30/19, 12:56 AM, "Elek, Marton" wrote:
>
> Thanks Eric the suggestions.
>
> Unfortunately (as Anu wrote it) our use-case is slightly different.
>
> It was
maven project version, which minimize
> version number management between maven and docker.
>
> Regards,
> Eric
>
> On 1/31/19, 8:59 AM, "Elek, Marton" wrote:
>
>
> Hi Eric,
>
> Thanks for the answers
>
>
+1 (non-binding)
(my arguments are in the discuss thread. small move, huge benefit)
Thanks,
Marton
On 2/1/19 11:15 PM, 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
+1 (non-binding)
- build from source
- run all the smoketest (from the fresh build based on the src package)
- run all the smoketest from the binary package
- signature files are checked
- sha512 checksums are verified
- ozone version shows the right commit information
Thanks Ajay all the
+1 (non-binding).
Thanks the continuous effort Ajay. This is the best Ozone release
package what I have ever seen:
I checked the following:
* Signatures are checked: OK
* sha512 checksums are checked: OK
* can be built from the source: OK
* smoketest executed from the bin package (after
Thanks the answers Eric Yang, I think we have similar view about how the
releases are working and what you wrote is exactly the reason why I
prefer the current method (docker image creation from separated branch)
instead of the proposed one (create images from maven).
1. Not all the branches can
TLDR; I propose to move Ozone related code out from Hadoop trunk and
store it in a separated *Hadoop* git repository apache/hadoop-ozone.git
When Ozone was adopted as a new Hadoop subproject it was proposed[1] to
be part of the source tree but with separated release cadence, mainly
oes for filesystem contract
tests.
are you happy with that?
On Tue, Sep 17, 2019 at 10:48 AM Elek, Marton wrote:
TLDR; I propose to move Ozone related code out from Hadoop trunk and
store it in a separated *Hadoop* git repository apache/hadoop-ozone.git
When Ozone was adopted as a new
+1 (binding)
Thanks Rohith the work with the release.
* built from the source (archlinux)
* verified signatures
* verified sha512 checksums
* started a docker-based pseudo cluster
* tested basic HDFS operations with CLI
* Checked if the sources are uploaded to the maven staging repo
Hi,
Github UI (ui!) helps to merge Pull Requests to the proposed branch.
There are three different ways to do it [1]:
1. Keep all the different commits from the PR branch and create one
additional merge commit ("Create a merge commit")
2. Squash all the commits and commit the change as one
Thanks for all the positive feedback,
I opened INFRA-18777 to request the proposed change.
Marton
On 7/18/19 10:02 AM, Masatake Iwasaki wrote:
> +1
>
> Thanks,
> Masatake Iwasaki
>
> On 7/17/19 15:07, Elek, Marton wrote:
>> Hi,
>>
>> Github U
As discussed earlier in the thread of "Hadoop-Ozone repository mailing
list configurations" [1] I suggested to solve the current
misconfiguration problem with creating separated mailing lists
(dev/issues) for Hadoop Ozone.
It would have some additional benefit: for example it would make
point
github to that?
On Sun, Oct 27, 2019 at 10:12 PM Dinesh Chitlangia
wrote:
+1
-Dinesh
On Sun, Oct 27, 2019, 4:25 AM Elek, Marton
As discussed earlier in the thread of "Hadoop-Ozone repository mailing
list configurations" [1] I suggested to solve the current
misconfiguration problem w
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
> Do you see a Submarine like split-also-into-a-TLP for Ozone? If not
now, sometime further down the line?
Good question, and I don't know what is the best answer right now. It's
definitely an option, But Submarine move hasn't been finished, so it's
not yet possible to learn form the
To be honest, I have no idea. I don't know about the historical meaning.
But as there is no other feedback, here are my guesses based on pure logic:
* current -> should point to the release with the highest number (3.2.1)
* stable -> to the stable 3.x release with the highest number (3.2.1
+1
Thank you Nanda the enormous work to make this release happen.
* GPG Signatures are fine
* SHA512 signatures are fine
* Can be built from the source package (in isolated environment
without cached hadoop/ozone artifacts)
* Started the pseudo cluster with `compose/ozone`
* Executed
Sure. Will do it that way.
Thanks the feedback.
Marton
On 10/12/19 7:27 PM, Vinod Kumar Vavilapalli wrote:
On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton wrote:
As the overall feedback was positive (in fact many of the answers were
simple +1 votes) I don't think the thread should
As discussed earlier Ozone is moved out from Hadoop trunk.
Please commit / create pull requests to the
--> https://github.com/apache/hadoop-ozone
in the future.
Remaining Ozone code will be deleted from Hadoop trunk with HDDS-2288.
Marton
Thank you very much to work on this release Vinay, 1.0.0 is always a
hard work...
1. I downloaded it and I can build it from the source
2. Checked the signature and the sha512 of the src package and they are fine
3. Yetus seems to be included in the source package. I am not sure if
it's
I would like to start a discussion to make a separate Apache project for
Ozone
### HISTORY [1]
* Apache Hadoop Ozone development started on a feature branch of
Hadoop repository (HDFS-7240)
* In the October of 2017 a discussion has been started to merge it to
the Hadoop main branch
One question, for the committers who contributed to Ozone before and got
the committer-role in the past (like me), will they carry the
committer-role to the new repo?
In short: yes.
In more details:
This discussion (if there is an agreement) should be followed by a next
discussion +
+1
* signatures checked
* sha512 checked
* can be built from the source (without using my local mvn cache:
using apache/ozone-build docker image)
* created docker image with the provided Dockerfile
* Deployed to Kubernetes together with Yarn and Hdfs
* tested with 100G teragen (one
+1 (binding)
1. verified signatures
2. verified checksums
3. verified the output of `ozone version` (includes the good git revision)
4. verified that the source package matches the git tag
5. verified source can be used to build Ozone without previous state
(docker run -v ... -it maven ...
Hi,
The Hadoop community earlier decided to move out Ozone sub-project to a
separated Apache Top Level Project (TLP). [1]
For detailed history and motivation, please check the previous thread ([1])
Ozone community discussed and agreed on the initial version of the
project proposal, and
The vote passes with 29 +1 (where 22 are binding) and without -1 or 0.
Thank you very much for all the votes/support.
As a next step, I will send the proposal and the result of this vote to
the ASF board.
Thanks again,
Marton
that there are some leftover
references to version "0.6.0" in upgrade scripts and tests
(HDDS-4139). Created a pull request to fix it, please consider
including it in the release.
thanks,
Attila
On Mon, Aug 24, 2020 at 3:55 PM Elek, Marton wrote:
+1 (binding)
1. verified sig
+1 (binding)
1. verified signatures
2. verified checksums
3. verified the output of `ozone version` (includes the good git revision)
4. verified that the source package matches the git tag
5. verified source can be used to build Ozone without previous state
(docker run -v ... -it maven
Hi all,
Thank you for all the feedback and requests,
As we discussed in the previous thread(s) [1], Ozone is proposed to be a
separated Apache Top Level Project (TLP)
The proposal with all the details, motivation and history is here:
Thank you all the feedback and update.
If there is no more comments, I will start the vote on Thursday.
Thanks,
Marton
On 9/7/20 2:04 PM, Elek, Marton wrote:
Hi,
The Hadoop community earlier decided to move out Ozone sub-project to a
separated Apache Top Level Project (TLP). [1
(based on the proposal) here
4. Voted proposal will be sent to the ASF board to be
discussed/decided/approved.
Thanks, again, all your feedback,
Marton
On 5/13/20 9:52 AM, Elek, Marton wrote:
I would like to start a discussion to make a separate Apache project for
Ozone
### HISTORY
+1 (binding)
* checked signature
* built from source
* deployed binary package to kubernetes
* executed teragen with automatic tests [1]
* checked "hadoop version" and compared with git revision
* checked if the staging repository contains src packages
Thanks the work (and the toughness)
On 6/19/20 7:19 PM, Owen O'Malley wrote:
We unfortunately have a lot of master/slave and whitelist/blacklist
terminology usage in Hadoop. It will take a while to fix them all, but one
is easy to fix. In particular, we have a "master" branch that hasn't been
used since the project
Elek, Marton created HADOOP-14160:
-
Summary: Create dev-support scripts to do the bulk jira update
required by the release process
Key: HADOOP-14160
URL: https://issues.apache.org/jira/browse/HADOOP-14160
Elek, Marton created HADOOP-14164:
-
Summary: Update the skin of maven-site during doc generation
Key: HADOOP-14164
URL: https://issues.apache.org/jira/browse/HADOOP-14164
Project: Hadoop Common
Elek, Marton created HADOOP-14162:
-
Summary: Improve release scripts to automate missing steps
Key: HADOOP-14162
URL: https://issues.apache.org/jira/browse/HADOOP-14162
Project: Hadoop Common
Elek, Marton created HADOOP-14163:
-
Summary: Refactor existing hadoop site to use more usable static
website generator
Key: HADOOP-14163
URL: https://issues.apache.org/jira/browse/HADOOP-14163
Elek, Marton created HADOOP-14898:
-
Summary: Create official Docker images for development and testing
features
Key: HADOOP-14898
URL: https://issues.apache.org/jira/browse/HADOOP-14898
Project
Elek, Marton created HADOOP-14850:
-
Summary: Read HttpServer2 resources directly from the source tree
(if exists)
Key: HADOOP-14850
URL: https://issues.apache.org/jira/browse/HADOOP-14850
Project
Elek, Marton created HADOOP-15065:
-
Summary: Make mapreduce specific GenericOptionsParser arguments
optional
Key: HADOOP-15065
URL: https://issues.apache.org/jira/browse/HADOOP-15065
Project: Hadoop
Elek, Marton created HADOOP-15122:
-
Summary: Lock down version of doxia-module-markdown plugin
Key: HADOOP-15122
URL: https://issues.apache.org/jira/browse/HADOOP-15122
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-14162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton resolved HADOOP-14162.
---
Resolution: Won't Fix
> Improve release scripts to automate missing st
[
https://issues.apache.org/jira/browse/HADOOP-14160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton resolved HADOOP-14160.
---
Resolution: Won't Fix
> Create dev-support scripts to do the bulk jira update requi
Elek, Marton created HADOOP-15084:
-
Summary: Create docker images for latest stable hadoop2 build
Key: HADOOP-15084
URL: https://issues.apache.org/jira/browse/HADOOP-15084
Project: Hadoop Common
Elek, Marton created HADOOP-15083:
-
Summary: Create base image for running hadoop in docker containers
Key: HADOOP-15083
URL: https://issues.apache.org/jira/browse/HADOOP-15083
Project: Hadoop Common
Elek, Marton created HADOOP-15539:
-
Summary: Make start-build-env.sh usable in non-interactive mode
Key: HADOOP-15539
URL: https://issues.apache.org/jira/browse/HADOOP-15539
Project: Hadoop Common
Elek, Marton created HADOOP-15256:
-
Summary: Create docker images for latest stable hadoop3 build
Key: HADOOP-15256
URL: https://issues.apache.org/jira/browse/HADOOP-15256
Project: Hadoop Common
Elek, Marton created HADOOP-15257:
-
Summary: Provide example docker compose file for developer builds
Key: HADOOP-15257
URL: https://issues.apache.org/jira/browse/HADOOP-15257
Project: Hadoop Common
Elek, Marton created HADOOP-15258:
-
Summary: Create example docker-compse file for documentations
Key: HADOOP-15258
URL: https://issues.apache.org/jira/browse/HADOOP-15258
Project: Hadoop Common
Elek, Marton created HADOOP-15656:
-
Summary: Support byteman in hadoop-runner baseimage
Key: HADOOP-15656
URL: https://issues.apache.org/jira/browse/HADOOP-15656
Project: Hadoop Common
Issue
Elek, Marton created HADOOP-15673:
-
Summary: Hadoop:3 image is missing from dockerhub
Key: HADOOP-15673
URL: https://issues.apache.org/jira/browse/HADOOP-15673
Project: Hadoop Common
Issue
Elek, Marton created HADOOP-15730:
-
Summary: Add Ozone submodule to the hadoop.apache.org
Key: HADOOP-15730
URL: https://issues.apache.org/jira/browse/HADOOP-15730
Project: Hadoop Common
Elek, Marton created HADOOP-15302:
-
Summary: Enable DataNode/NameNode service plugins with Service
Provider interface
Key: HADOOP-15302
URL: https://issues.apache.org/jira/browse/HADOOP-15302
Project
Elek, Marton created HADOOP-15367:
-
Summary: Update the initialization code in the docker
hadoop-runner baseimage
Key: HADOOP-15367
URL: https://issues.apache.org/jira/browse/HADOOP-15367
Project
Elek, Marton created HADOOP-15369:
-
Summary: Avoid usage of ${project.version} in parent pom
Key: HADOOP-15369
URL: https://issues.apache.org/jira/browse/HADOOP-15369
Project: Hadoop Common
Elek, Marton created HADOOP-15352:
-
Summary: FIx default local maven repository path in create-release
script
Key: HADOOP-15352
URL: https://issues.apache.org/jira/browse/HADOOP-15352
Project
Elek, Marton created HADOOP-15353:
-
Summary: Bump default yetus version in the yetus-wrapper
Key: HADOOP-15353
URL: https://issues.apache.org/jira/browse/HADOOP-15353
Project: Hadoop Common
Elek, Marton created HADOOP-15339:
-
Summary: Support additional key/value propereties in JMX bean
registration
Key: HADOOP-15339
URL: https://issues.apache.org/jira/browse/HADOOP-15339
Project
Elek, Marton created HADOOP-15340:
-
Summary: Fix the RPC server name usage to provide information
about the metrics
Key: HADOOP-15340
URL: https://issues.apache.org/jira/browse/HADOOP-15340
Project
Elek, Marton created HADOOP-15857:
-
Summary: Remove ozonefs class name definition from core-default.xml
Key: HADOOP-15857
URL: https://issues.apache.org/jira/browse/HADOOP-15857
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-15339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elek, Marton reopened HADOOP-15339:
---
Since the commit we use this change from ozone/hdds and it worked well.
This change
Elek, Marton created HADOOP-15791:
-
Summary: Remove Ozone related sources from the 3.2 branch
Key: HADOOP-15791
URL: https://issues.apache.org/jira/browse/HADOOP-15791
Project: Hadoop Common
Elek, Marton created HADOOP-16063:
-
Summary: Docker based pseudo-cluster definitions and test scripts
for Hdfs/Yarn
Key: HADOOP-16063
URL: https://issues.apache.org/jira/browse/HADOOP-16063
Project
Elek, Marton created HADOOP-16064:
-
Summary: Load configuration values from external sources
Key: HADOOP-16064
URL: https://issues.apache.org/jira/browse/HADOOP-16064
Project: Hadoop Common
Elek, Marton created HADOOP-16003:
-
Summary: Migrate the Hadoop jenkins jobs to use new gitbox urls
Key: HADOOP-16003
URL: https://issues.apache.org/jira/browse/HADOOP-16003
Project: Hadoop Common
Elek, Marton created HADOOP-16146:
-
Summary: Make start-build-env.sh safe in case of misusage of
DOCKER_INTERACTIVE_RUN
Key: HADOOP-16146
URL: https://issues.apache.org/jira/browse/HADOOP-16146
1 - 100 of 108 matches
Mail list logo
