Github user asfgit closed the pull request at:
https://github.com/apache/hadoop/pull/78
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Hi Junping, thanks for the mail, inline:
On Sat, Feb 20, 2016 at 7:34 AM, Junping Du wrote:
> Shall we consolidate effort for 2.8.0 and 3.0.0? It doesn't sounds
> reasonable to have two alpha releases to go in parallel. Is EC feature the
> main motivation of releasing hadoop 3 here? If so, I don
Here is a pull request for the changes needed to have hadoop access
archive.org s3,
https://github.com/apache/hadoop/pull/79
I now have access to archive.org working in my test case.
See my test case here :
https://github.com/h4ck3rm1k3/hadoop-archive-org-bucket-fs
new URI("s3://bucketname").ge
GitHub user h4ck3rm1k3 opened a pull request:
https://github.com/apache/hadoop/pull/79
for archive.org
I now have access to archive.org working.
See my test case here :
https://github.com/h4ck3rm1k3/hadoop-archive-org-bucket-fs
new URI("s3://bucketname").getHost()
GitHub user arp7 opened a pull request:
https://github.com/apache/hadoop/pull/78
HDFS-9839. Reduce verbosity of processReport logging
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/arp7/hadoop HDFS-9839
Alternatively you can re
Shall we consolidate effort for 2.8.0 and 3.0.0? It doesn't sounds reasonable
to have two alpha releases to go in parallel. Is EC feature the main motivation
of releasing hadoop 3 here? If so, I don't understand why this feature cannot
land on 2.8.x or 2.9.x as an alpha feature.
If we release 3
Le 20/02/2016 12:15, Benedikt Ritter a écrit :
> Anything missing?
Define the scope of the project? Do we go after Bouncy Castle and aim
for an equivalent feature set?
Emmanuel Bourg
Hi,
I'd like to discuss the next steps for moving the Chimera component to
Apache Commons. So far, none of the other PMC members has expressed his or
her thoughts about this. If nobody brings up objections about moving the
component to Apache Commons, I'm assuming lazy consensus about this.
So th
