IMO, if part of the community wants to take on the responsibility and work
that takes to do a new major release, we should not discourage them from
doing that.
Having multiple major branches active is a standard practice.
This time around we are not replacing the guts as we did from Hadoop 1 to
The 'resistance' is not so much about a new major release, more so about the
content and the roadmap of the release. Other than the two specific features
raised (the need for breaking compat for them is something that I am debating),
I haven't seen a roadmap of branch-3 about any more features
Sean Busbey created HADOOP-11680:
Summary: Deduplicate jars in convenience binary distribution
Key: HADOOP-11680
URL: https://issues.apache.org/jira/browse/HADOOP-11680
Project: Hadoop Common
Sorry, outlook dequoted Alejandros's comments.
Let me try again with his comments in italic and proofreading of mine
On 05/03/2015 13:59, Steve Loughran
ste...@hortonworks.commailto:ste...@hortonworks.com wrote:
On 05/03/2015 13:05, Alejandro Abdelnur
I'm OK with a 3.0.0 release as long as we are minimizing the pain of
maintaining yet another release line and conscious of the incompatibilities
going into that release line.
For the former, I would really rather not see a branch-3 cut so soon. It's yet
another line onto which to cherry-pick,
Duo Xu created HADOOP-11681:
---
Summary: HBase gives up retries after being throttled by Azure
storage
Key: HADOOP-11681
URL: https://issues.apache.org/jira/browse/HADOOP-11681
Project: Hadoop Common
The 2.7 blocker JIRA went down and going back up again, we will need to
converge.
Unless I see objections, I plan to cut a branch this weekend and selectively
filter stuff in after that in the interest of convergence.
Thoughts welcome!
Thanks,
+Vinod
On Mar 1, 2015, at 11:58 AM, Arun Murthy
Tx for the feedback! Let's continue on JIRA, but I'd definitely welcome as much
help as is available.
Thanks,
+Vinod
On Mar 4, 2015, at 3:30 PM, Zhijie Shen zs...@hortonworks.com wrote:
+1. It¹s really helpful for branch development. To continue Karthik¹s
point, is it good make pre-commit
On 05/03/2015 13:05, Alejandro Abdelnur
tuc...@gmail.commailto:tuc...@gmail.com wrote:
IMO, if part of the community wants to take on the responsibility and work
that takes to do a new major release, we should not discourage them from
doing that.
Having multiple major branches active is a
I think it'll be useful to have a discussion about what else people would
like to see in Hadoop 3.x - especially if the change is potentially
incompatible. Also, what we expect the release schedule to be for major
releases and what triggers them - JVM version, major features, the need for
If classloader isolation is in place, then dependency versions can freely
be upgraded as won't pollute apps space (things get trickier if there is an
ON/OFF switch).
On Thu, Mar 5, 2015 at 9:21 PM, Allen Wittenauer a...@altiscale.com wrote:
Is there going to be a general upgrade of
Haohui Mai created HADOOP-11682:
---
Summary: Move the native code for libhadoop into a dedicated
directory
Key: HADOOP-11682
URL: https://issues.apache.org/jira/browse/HADOOP-11682
Project: Hadoop Common
I've taken the liberty of adding a Hadoop 3 section to the Roadmap wiki
page. In addition to the two things I've been pushing, I also looked
through Allen's list (thanks Allen for making this) and picked out the
shell script rewrite and the removal of HFTP as big changes. This would be
the place
Thanks all.
There is an open issue HDFS-6962 (ACLs inheritance conflicts with
umaskmode), for which the incompatibility appears to make it not suitable
for 2.x and it's targetted 3.0, please see:
On Mon, Mar 2, 2015 at 11:04 PM, Konstantin Shvachko
shv.had...@gmail.com wrote:
2. If Hadoop 3 and 2.x are meant to exist together, we run a risk to
manifest split-brain behavior again, as we had with hadoop-1, hadoop-2 and
other versions. If that somehow beneficial for commercial vendors,
Haohui Mai created HADOOP-11679:
---
Summary: Create build infrastructure for the native RPC client
Key: HADOOP-11679
URL: https://issues.apache.org/jira/browse/HADOOP-11679
Project: Hadoop Common
Hello Leo/Liou
And the plugin interface can be as simple as this function (error handling
ignored here) ...
I thought it's good to have the pluggable allowing to customize the method how
to perform the mapping.
You could open a JIRA for this. If you'd like to work on it and need help,
See https://builds.apache.org/job/Hadoop-common-trunk-Java8/125/changes
Changes:
[wheat9] HDFS-7879. hdfs.dll does not export functions of the public libhdfs
API. Contributed by Chris Nauroth.
[jlowe] YARN-3131. YarnClientImpl should check FAILED and KILLED state in
submitApplication.
Matthew Willson created HADOOP-11678:
Summary: AvroSerializer buffers output in violation of contract
for Serializer
Key: HADOOP-11678
URL: https://issues.apache.org/jira/browse/HADOOP-11678
nijel created HADOOP-11677:
--
Summary: Missing secure session attributed for log and static
contexts
Key: HADOOP-11677
URL: https://issues.apache.org/jira/browse/HADOOP-11677
Project: Hadoop Common
Walter Su created HADOOP-11676:
--
Summary: Add API to NetworkTopology for getting all racks
Key: HADOOP-11676
URL: https://issues.apache.org/jira/browse/HADOOP-11676
Project: Hadoop Common
Issue
[
https://issues.apache.org/jira/browse/HADOOP-11475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsuyoshi Ozawa reopened HADOOP-11475:
-
Utilize try-with-resource to close StopWatch
Sunny Cheung created HADOOP-11683:
-
Summary: Need a plugin API to translate long principal names to
local OS user names arbitrarily
Key: HADOOP-11683
URL: https://issues.apache.org/jira/browse/HADOOP-11683
23 matches
Mail list logo
