[
https://issues.apache.org/jira/browse/HADOOP-10932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xukun reopened HADOOP-10932:
compile error on project Apache Hadoop OpenStack support
[
https://issues.apache.org/jira/browse/HADOOP-10932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xukun resolved HADOOP-10932.
Resolution: Duplicate
compile error on project Apache Hadoop OpenStack support
See https://builds.apache.org/job/Hadoop-Common-trunk/1196/changes
Changes:
[vinayakumarb] HDFS-5185. DN fails to startup if one of the data dir is full.
Contributed by Vinayakumar B.
[vinayakumarb] HDFS-5723. Append failed FINALIZED replica should not be
accepted as valid when that block is
I'm =0 on convenience, but like you said, that's because most people have
drifted into public/private git repos for development of branches (though
that's partly to avoid the ongoing review-before-each commit overhead)
-moving to Git could encourage more in-ASF branch dev by committers
-if we
[
https://issues.apache.org/jira/browse/HADOOP-10886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G resolved HADOOP-10886.
--
Resolution: Fixed
Hadoop Flags: Reviewed
CryptoCodec#getCodecclasses
merging a multi jiras feature from one branch to another is much easier in git,
you can keep all jiras as single commits, you can do any necessary rebasing
locally, you cant tweak CHANGES.txt locally, tweak and rebase and squash as
necessary, check everything locally, iterate, then push when
Personally, I would love us to use something like gerrit.
My current review workflow requires me to download the patch, apply it on
latest trunk and look at the diff in an IDE. I still might want to do it
for big patches, but I would love to be able to just see the diff directly.
Also, it would
HBase recently made the leap from SVN to Git. Our early experience is
positive, I think. My observations:
When you commit a merge in git, the software will generate a merge commit
message in the target branch's history. HBasers decided these pollute
history - although an option to 'git log' can
+1 to going with git, and +1 to a rebase flow if we do so.
On Mon, Aug 4, 2014 at 10:43 AM, Andrew Purtell apurt...@apache.org wrote:
HBase recently made the leap from SVN to Git. Our early experience is
positive, I think. My observations:
When you commit a merge in git, the software will
Brian Loss created HADOOP-10934:
---
Summary: AbstractCounters.readFields doesn't clear other groups
Key: HADOOP-10934
URL: https://issues.apache.org/jira/browse/HADOOP-10934
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah resolved HADOOP-9741.
-
Resolution: Won't Fix
Make build created indexed jars
---
Allen Wittenauer created HADOOP-10935:
-
Summary: Cleanup HadoopKerberosName for public consumption
Key: HADOOP-10935
URL: https://issues.apache.org/jira/browse/HADOOP-10935
Project: Hadoop Common
neat, didn't know about the selective force push.
On Mon, Aug 4, 2014 at 10:43 AM, Andrew Purtell apurt...@apache.org wrote:
HBase recently made the leap from SVN to Git. Our early experience is
positive, I think. My observations:
When you commit a merge in git, the software will generate a
Andrew Wang created HADOOP-10936:
Summary: Change default KeyProvider bitlength to 128
Key: HADOOP-10936
URL: https://issues.apache.org/jira/browse/HADOOP-10936
Project: Hadoop Common
Issue
[
https://issues.apache.org/jira/browse/HADOOP-6297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin J. Price resolved HADOOP-6297.
Resolution: Won't Fix
As JDK 7 provides support for this functionality in the basic Java
Arun Suresh created HADOOP-10937:
Summary: Fix NullPointerException when touchz-ing a file
Key: HADOOP-10937
URL: https://issues.apache.org/jira/browse/HADOOP-10937
Project: Hadoop Common
Thank you for great suggestion, Karthik. +1(non-binding) to use git.
I'm also using private git repository.
Additionally, I have one question. Will we accept github-based
development like Apache Spark? IHMO, it allow us to leverage Hadoop
development, because the cost of sending pull request is
I think we should take things one step at a time. Switching to git
definitely opens up the possibility for better review workflows, but we can
discuss that on a different thread.
A few different people have also mentioned Gerrit, so that'd be in the
running along with Github (and I guess
Thank you for supplementation, Andrew. Yes, we should go step by step
and let's discuss review workflows on a another thread.
Thanks,
- Tsuyoshi
On Tue, Aug 5, 2014 at 8:23 AM, Andrew Wang andrew.w...@cloudera.com wrote:
I think we should take things one step at a time. Switching to git
Yi Liu created HADOOP-10938:
---
Summary: Remove thread-safe description in PositionedReadable
javadoc
Key: HADOOP-10938
URL: https://issues.apache.org/jira/browse/HADOOP-10938
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-10600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kai Zheng resolved HADOOP-10600.
Resolution: Duplicate
Release Note: Per Zhijie's request, resolve this as a duplicate of
21 matches
Mail list logo
