[
https://issues.apache.org/jira/browse/HADOOP-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
aaaliu resolved HADOOP-11745.
-
Resolution: Fixed
Assignee: aaaliu
Hadoop Flags: Reviewed
> Incorporate ShellCheck static
[
https://issues.apache.org/jira/browse/HADOOP-11805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kai Zheng resolved HADOOP-11805.
Resolution: Fixed
Fix Version/s: HDFS-7285
> Better to rename some raw erasure coders
> ---
[
https://issues.apache.org/jira/browse/HADOOP-11645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinayakumar B resolved HADOOP-11645.
Resolution: Fixed
Fix Version/s: HDFS-7285
Hadoop Flags: Reviewed
Thanks [~dra
Find and fix the mistake made in the past 24 hours to the git log (and
changes.txt as well, so no help there!).
[
https://issues.apache.org/jira/browse/HADOOP-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer reopened HADOOP-11745:
---
Assignee: Allen Wittenauer (was: aaaliu)
> Incorporate ShellCheck static analysis
On Apr 7, 2015, at 8:56 AM, Allen Wittenauer wrote:
>
> Find and fix the mistake made in the past 24 hours to the git log (and
> changes.txt as well, so no help there!).
>
>
… and no, it isn’t that YARN-2666 is missing it’s JIRA in the changes.txt.
That’s too easy and besides, I sai
Is this a trick question, because you really can't "fix" prior commits in
the git log without a forced push, which then invalidates everyone's
cloned copy of the repo? :-)
Chris Nauroth
Hortonworks
http://hortonworks.com/
On 4/7/15, 9:55 AM, "Allen Wittenauer" wrote:
>
>On Apr 7, 2015, at
On Apr 7, 2015, at 10:03 AM, Chris Nauroth wrote:
> Is this a trick question, because you really can't "fix" prior commits in
> the git log without a forced push, which then invalidates everyone's
> cloned copy of the repo? :-)
There is an error that would require such a thing, yes. :D
pascal oliva created HADOOP-11810:
-
Summary: Test TestSecureRMRegistryOperations failed with IBM_JAVA
JVM
Key: HADOOP-11810
URL: https://issues.apache.org/jira/browse/HADOOP-11810
Project: Hadoop Comm
[
https://issues.apache.org/jira/browse/HADOOP-11809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arpit Agarwal resolved HADOOP-11809.
Resolution: Invalid
Hi [~kantum...@yahoo.com], please use the dev mailing list for questio
A proper precommit hook could have prevented YARN-2666 mishap.
On Tue, Apr 7, 2015 at 9:55 AM, Allen Wittenauer wrote:
>
> On Apr 7, 2015, at 8:56 AM, Allen Wittenauer wrote:
>
> >
> > Find and fix the mistake made in the past 24 hours to the git log (and
> changes.txt as well, so no help there
Chen He created HADOOP-11811:
Summary: Fix typos in hadoop-project/pom.xml
Key: HADOOP-11811
URL: https://issues.apache.org/jira/browse/HADOOP-11811
Project: Hadoop Common
Issue Type: Bug
For those wondering, YARN-2429 is the wrong JIRA for that commit. Simple typo,
but deadly if one is using to use the git log to determine what’s actually
committed...
All,
I am trying to build hadoop 2.6.0 on Windows 7 64 bit, Windows 7.1 SDK. I have
gone through Build.txt file and have did follow all the pre-requisites for
build on windows. Still when I try to build, I am getting following error:
Maven command: mvn package -X -Pdist -Pdocs -Psrc -Dtar -Dski
The solution to this problem (if it is really a problem) is to keep
around a side file with some errata. I have such a side file that I
use with my script which compares two branches via git log. There's
always commits where the wrong message got applied, or the jira number
was missing, or etc.
Oops, sorry for YARN-2666. I forgot to include JIRA number in git repository.
I'll see to it more and more based on the result of this discussion.
- Tsuyoshi
On Wed, Apr 8, 2015 at 10:13 AM, Colin P. McCabe wrote:
> The solution to this problem (if it is really a problem) is to keep
> around a s
16 matches
Mail list logo
