Let's not dismiss this quite so handily.
Sean, Jason, and Stack replied on HADOOP-11656 pointing out that while we
could make classpath isolation opt-in via configuration, what we really
want longer term is to have it on by default (or just always on). Stack in
particular points out the practical
Thanks for reviving this on email, Vinod. Newer folks like me might not be
aware of this JIRA/effort.
This would be wonderful to have so (1) we know the status of release
branches (branch-2, etc.) and also (2) feature branches (YARN-2928).
Jonathan's or Matt's proposal for including branch name
+1
If we can make things look like HBase support for precommit testing on
branches (HBASE-12944), that would make it easier for new and occasional
contributors who might end up working in other ecosystem projects. AFAICT,
Jonathan's proposal for branch names in patch names does this.
On Wed,
Hi all,
I'd like us to revive the effort at
https://issues.apache.org/jira/browse/HADOOP-7435 to make precommit builds
being able to work with branches. Having the Jenkins verify patches on branches
is very useful even if there may be relaxed review oversight on the said-branch.
Unless there
In general +1 on 3.0.0. Its time. If we start now, it might make it out by
2016. If we start now, downstreamers can start aligning themselves to land
versions that suit at about the same time.
While two big items have been called out as possible incompatible changes,
and there is ongoing
[
https://issues.apache.org/jira/browse/HADOOP-11668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer reopened HADOOP-11668:
---
Assignee: Allen Wittenauer (was: Vinayakumar B)
Re-opening. The problem here
Thanks Vinod for the hints.
I have updated the both patches aligning with latest codes, and added more unit
tests. The building results look reasonable. Thanks anyone that would give them
more review and I would update in timely manner.
Regards,
Kai
-Original Message-
From: Vinod
Adam Budde created HADOOP-11670:
---
Summary: Fix IAM instance profile auth for s3a (broken in
HADOOP-11446)
Key: HADOOP-11670
URL: https://issues.apache.org/jira/browse/HADOOP-11670
Project: Hadoop
Might I have some comments for this, just providing my thought. Thanks.
If we start now, it might make it out by 2016. If we start now,
downstreamers can start aligning themselves to land versions that suit at
about the same time.
Not only for down streamers to align with the long term
Tsuyoshi Ozawa sent out an email to the common-dev list about this
recently. It seems like the bug only bites when the number of
elements is larger than 67108864, which may limit its impact (to state
it mildly). Also, the flawed sorting algorithm is not used on arrays
of primitives, just on
Akira AJISAKA created HADOOP-11673:
--
Summary: Use org.junit.Assume to skip tests instead of return
Key: HADOOP-11673
URL: https://issues.apache.org/jira/browse/HADOOP-11673
Project: Hadoop Common
+1. It¹s really helpful for branch development. To continue Karthik¹s
point, is it good make pre-commit testing against branch-2 as the default
too like that against trunk?
On 3/4/15, 1:47 PM, Sean Busbey bus...@cloudera.com wrote:
+1
If we can make things look like HBase support for precommit
xiangqian.xu created HADOOP-11672:
-
Summary: test
Key: HADOOP-11672
URL: https://issues.apache.org/jira/browse/HADOOP-11672
Project: Hadoop Common
Issue Type: New Feature
Sean Busbey created HADOOP-11674:
Summary: data corruption for parallel CryptoInputStream and
CryptoOutputStream
Key: HADOOP-11674
URL: https://issues.apache.org/jira/browse/HADOOP-11674
Project:
[
https://issues.apache.org/jira/browse/HADOOP-11643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kai Zheng resolved HADOOP-11643.
Resolution: Fixed
Target Version/s: HDFS-7285
Hadoop Flags: Reviewed
Define EC
Sorry I was not clear enough about the problem. Let me explain more here.
Our problem is that normal user principal names can be very different from
their Unix login. Some customers simply have arbitrary mapping between their
Kerberos principals and Unix user accounts. For example, one customer
One of the questions that keeps popping up is “what exactly is in trunk?”
As some may recall, I had done some experiments creating the change log based
upon JIRA. While the interest level appeared to be approaching zero, I kept
playing with it a bit and eventually also started playing with
[
https://issues.apache.org/jira/browse/HADOOP-11672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brahma Reddy Battula resolved HADOOP-11672.
---
Resolution: Not a Problem
test
Key: HADOOP-11672
Liang Xie created HADOOP-11675:
--
Summary: tiny exception log with checking storedBlock is null or
not
Key: HADOOP-11675
URL: https://issues.apache.org/jira/browse/HADOOP-11675
Project: Hadoop Common
See https://builds.apache.org/job/Hadoop-Common-trunk/1424/changes
20 matches
Mail list logo
