[jira] [Commented] (MAPREDUCE-4923) Add toString method to TaggedInputSplit
[ https://issues.apache.org/jira/browse/MAPREDUCE-4923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553555#comment-13553555 ] Harsh J commented on MAPREDUCE-4923: This looks good; shall we also mark TaggedInputSplit public for those who wish to determine logic based on Context.getInputSplit()? > Add toString method to TaggedInputSplit > --- > > Key: MAPREDUCE-4923 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4923 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv1, mrv2, task >Affects Versions: 1.1.1, 2.0.2-alpha >Reporter: Sandy Ryza >Assignee: Sandy Ryza >Priority: Minor > Attachments: MAPREDUCE-4923-branch-1.patch, MAPREDUCE-4923.patch > > > Per MAPREDUCE-3678, map task logs now contain information about the input > split being processed. Because TaggedInputSplit has no overridden toString > method, nothing useful gets printed out. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4942) mapreduce.Job has a bunch of methods that throw InterruptedException so its incompatible with MR1
[
https://issues.apache.org/jira/browse/MAPREDUCE-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553442#comment-13553442
]
Karthik Kambatla commented on MAPREDUCE-4942:
-
Hey Robert - from MAPREDUCE-4932, it seems like getTaskCompletionEvents(int,
int) doesn't exist in MR1. Shouldn't we skip it from this list here? In
MAPREDUCE-4932, we can implement getTaskCompletionEvents(int) without an
InterruptedException. What do you think?
> mapreduce.Job has a bunch of methods that throw InterruptedException so its
> incompatible with MR1
> -
>
> Key: MAPREDUCE-4942
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4942
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
>Affects Versions: 2.0.2-alpha
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>
> The following methods in MR2's {{org.apache.hadoop.mapreduce.Job}} throw an
> {{InterruptedException}} but don't in MR1, which makes them incompatible.
> (Their Javadoc comments are also missing that they throw an
> {{InterruptedException}} anyway)
> I propose that we wrap the {{InterruptedException}} in a
> {{RuntimeException}}.
> {code}
> public float setupProgress() throws IOException, InterruptedException
> public float mapProgress() throws IOException, InterruptedException
> public float reduceProgress() throws IOException, InterruptedException
> public boolean isComplete() throws IOException, InterruptedException
> public boolean isSuccessful() throws IOException, InterruptedException
> public void killJob() throws IOException, InterruptedException
> public TaskCompletionEvent[] getTaskCompletionEvents(int, int) throws
> IOException, InterruptedException
> public void killTask(org.apache.hadoop.mapreduce.TaskAttemptID) throws
> IOException, InterruptedException
> public void failTask(org.apache.hadoop.mapreduce.TaskAttemptID) throws
> IOException, InterruptedException
> public Counters getCounters() throws IOException, InterruptedException
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-1700) User supplied dependencies may conflict with MapReduce system JARs
[ https://issues.apache.org/jira/browse/MAPREDUCE-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553420#comment-13553420 ] Scott Carey commented on MAPREDUCE-1700: Awesome! > User supplied dependencies may conflict with MapReduce system JARs > -- > > Key: MAPREDUCE-1700 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-1700 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: task >Reporter: Tom White >Assignee: Tom White > Fix For: 2.0.3-alpha > > Attachments: MAPREDUCE-1700-ccl.patch, MAPREDUCE-1700-ccl.patch, > MAPREDUCE-1700.patch, MAPREDUCE-1700.patch, MAPREDUCE-1700.patch, > MAPREDUCE-1700.patch, MAPREDUCE-1700.patch, MAPREDUCE-1700.patch, > MAPREDUCE-1700.patch, MAPREDUCE-1700.patch > > > If user code has a dependency on a version of a JAR that is different to the > one that happens to be used by Hadoop, then it may not work correctly. This > happened with user code using a different version of Avro, as reported > [here|https://issues.apache.org/jira/browse/AVRO-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852081#action_12852081]. > The problem is analogous to the one that application servers have with WAR > loading. Using a specialized classloader in the Child JVM is probably the way > to solve this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4942) mapreduce.Job has a bunch of methods that throw InterruptedException so its incompatible with MR1
[
https://issues.apache.org/jira/browse/MAPREDUCE-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553385#comment-13553385
]
Robert Kanter commented on MAPREDUCE-4942:
--
In MR1, those methods don't do anything that could cause an
{{InterruptedException}}, so it wasn't an issue.
> mapreduce.Job has a bunch of methods that throw InterruptedException so its
> incompatible with MR1
> -
>
> Key: MAPREDUCE-4942
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4942
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
>Affects Versions: 2.0.2-alpha
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>
> The following methods in MR2's {{org.apache.hadoop.mapreduce.Job}} throw an
> {{InterruptedException}} but don't in MR1, which makes them incompatible.
> (Their Javadoc comments are also missing that they throw an
> {{InterruptedException}} anyway)
> I propose that we wrap the {{InterruptedException}} in a
> {{RuntimeException}}.
> {code}
> public float setupProgress() throws IOException, InterruptedException
> public float mapProgress() throws IOException, InterruptedException
> public float reduceProgress() throws IOException, InterruptedException
> public boolean isComplete() throws IOException, InterruptedException
> public boolean isSuccessful() throws IOException, InterruptedException
> public void killJob() throws IOException, InterruptedException
> public TaskCompletionEvent[] getTaskCompletionEvents(int, int) throws
> IOException, InterruptedException
> public void killTask(org.apache.hadoop.mapreduce.TaskAttemptID) throws
> IOException, InterruptedException
> public void failTask(org.apache.hadoop.mapreduce.TaskAttemptID) throws
> IOException, InterruptedException
> public Counters getCounters() throws IOException, InterruptedException
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4942) mapreduce.Job has a bunch of methods that throw InterruptedException so its incompatible with MR1
[
https://issues.apache.org/jira/browse/MAPREDUCE-4942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553383#comment-13553383
]
Sandy Ryza commented on MAPREDUCE-4942:
---
How was it dealt with in MR1?
> mapreduce.Job has a bunch of methods that throw InterruptedException so its
> incompatible with MR1
> -
>
> Key: MAPREDUCE-4942
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4942
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
>Affects Versions: 2.0.2-alpha
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>
> The following methods in MR2's {{org.apache.hadoop.mapreduce.Job}} throw an
> {{InterruptedException}} but don't in MR1, which makes them incompatible.
> (Their Javadoc comments are also missing that they throw an
> {{InterruptedException}} anyway)
> I propose that we wrap the {{InterruptedException}} in a
> {{RuntimeException}}.
> {code}
> public float setupProgress() throws IOException, InterruptedException
> public float mapProgress() throws IOException, InterruptedException
> public float reduceProgress() throws IOException, InterruptedException
> public boolean isComplete() throws IOException, InterruptedException
> public boolean isSuccessful() throws IOException, InterruptedException
> public void killJob() throws IOException, InterruptedException
> public TaskCompletionEvent[] getTaskCompletionEvents(int, int) throws
> IOException, InterruptedException
> public void killTask(org.apache.hadoop.mapreduce.TaskAttemptID) throws
> IOException, InterruptedException
> public void failTask(org.apache.hadoop.mapreduce.TaskAttemptID) throws
> IOException, InterruptedException
> public Counters getCounters() throws IOException, InterruptedException
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-4942) mapreduce.Job has a bunch of methods that throw InterruptedException so its incompatible with MR1
Robert Kanter created MAPREDUCE-4942:
Summary: mapreduce.Job has a bunch of methods that throw
InterruptedException so its incompatible with MR1
Key: MAPREDUCE-4942
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4942
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: mrv2
Affects Versions: 2.0.2-alpha
Reporter: Robert Kanter
Assignee: Robert Kanter
The following methods in MR2's {{org.apache.hadoop.mapreduce.Job}} throw an
{{InterruptedException}} but don't in MR1, which makes them incompatible.
(Their Javadoc comments are also missing that they throw an
{{InterruptedException}} anyway)
I propose that we wrap the {{InterruptedException}} in a {{RuntimeException}}.
{code}
public float setupProgress() throws IOException, InterruptedException
public float mapProgress() throws IOException, InterruptedException
public float reduceProgress() throws IOException, InterruptedException
public boolean isComplete() throws IOException, InterruptedException
public boolean isSuccessful() throws IOException, InterruptedException
public void killJob() throws IOException, InterruptedException
public TaskCompletionEvent[] getTaskCompletionEvents(int, int) throws
IOException, InterruptedException
public void killTask(org.apache.hadoop.mapreduce.TaskAttemptID) throws
IOException, InterruptedException
public void failTask(org.apache.hadoop.mapreduce.TaskAttemptID) throws
IOException, InterruptedException
public Counters getCounters() throws IOException, InterruptedException
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4932) mapreduce.job#getTaskCompletionEvents incompatible with MR1
[
https://issues.apache.org/jira/browse/MAPREDUCE-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated MAPREDUCE-4932:
-
Description:
In MR1, {{org.apache.hadoop.mapreduce.Job#getTaskCompletionEvents}} takes one
argument: {{int startFrom}}. In MR2, it now takes an additional argument:
{{int numEvents}} (which is the max number of events to get). This makes them
incompatible.
I propose we add a second {{getTaskCompletionEvents}} method that simply calls
the other one with {{numEvents}} set to {{Integer.MAX_VALUE}} to replicate the
behavior of the MR1 version.
was:
In MR1, {{org.apache.hadoop.mapreduce.Job#getTaskCompletionEvents}} takes one
argument: {{int startFrom}}. In MR2, it now takes an additional argument: {{
int numEvents}} (which is the max number of events to get). This makes them
incompatible.
I propose we add a second {{getTaskCompletionEvents}} method that simply calls
the other one with {{numEvents}} set to {{Integer.MAX_VALUE}} to replicate the
behavior of the MR1 version.
> mapreduce.job#getTaskCompletionEvents incompatible with MR1
> ---
>
> Key: MAPREDUCE-4932
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4932
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
>Affects Versions: 2.0.2-alpha
>Reporter: Robert Kanter
>Assignee: Robert Kanter
> Attachments: MAPREDUCE-4932.patch
>
>
> In MR1, {{org.apache.hadoop.mapreduce.Job#getTaskCompletionEvents}} takes one
> argument: {{int startFrom}}. In MR2, it now takes an additional argument:
> {{int numEvents}} (which is the max number of events to get). This makes
> them incompatible.
> I propose we add a second {{getTaskCompletionEvents}} method that simply
> calls the other one with {{numEvents}} set to {{Integer.MAX_VALUE}} to
> replicate the behavior of the MR1 version.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4938) Job submission to unknown queue can leave staging directory behind
[ https://issues.apache.org/jira/browse/MAPREDUCE-4938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553310#comment-13553310 ] Hudson commented on MAPREDUCE-4938: --- Integrated in Hadoop-trunk-Commit #3230 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3230/]) MAPREDUCE-4938. Use token request messages defined in hadoop common. Contributed by Suresh Srinvias. (Revision 1433227) Result = SUCCESS suresh : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1433227 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/api/impl/pb/client/MRClientProtocolPBClientImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/api/impl/pb/service/MRClientProtocolPBServiceImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/api/protocolrecords/impl/pb/CancelDelegationTokenRequestPBImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/api/protocolrecords/impl/pb/CancelDelegationTokenResponsePBImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/api/protocolrecords/impl/pb/GetDelegationTokenRequestPBImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/api/protocolrecords/impl/pb/GetDelegationTokenResponsePBImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/api/protocolrecords/impl/pb/RenewDelegationTokenRequestPBImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/api/protocolrecords/impl/pb/RenewDelegationTokenResponsePBImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/proto/MRClientProtocol.proto * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/proto/mr_service_protos.proto > Job submission to unknown queue can leave staging directory behind > -- > > Key: MAPREDUCE-4938 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4938 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: client >Affects Versions: 2.0.3-alpha, 0.23.5 >Reporter: Jason Lowe > > There is a race where submitting a job to an unknown queue can appear to > succeed to the client and then subsequently fail later. Since there was no > AM ever launched, there was nothing left to cleanup the staging directory. > At that point the client is the only thing that can cleanup the staging > directory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4928) Use token request messages defined in hadoop common
[ https://issues.apache.org/jira/browse/MAPREDUCE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated MAPREDUCE-4928: --- Resolution: Fixed Fix Version/s: 2.0.3-alpha Target Version/s: 2.0.3-alpha Release Note: Protobuf message GetDelegationTokenRequestProto field renewer is made requried from optional. This change is not wire compatible with the older releases. Hadoop Flags: Incompatible change,Reviewed (was: Incompatible change) Status: Resolved (was: Patch Available) I committed the patch to trunk and branch-2. Thank you Sid for the review. > Use token request messages defined in hadoop common > > > Key: MAPREDUCE-4928 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4928 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: applicationmaster, security >Reporter: Suresh Srinivas >Assignee: Suresh Srinivas > Fix For: 2.0.3-alpha > > Attachments: MR-4928.patch, MR-4928.patch, MR-4928.patch, > MR-4928.patch > > > MapReduce changes related to HADOOP-9192 to reuse the protobuf messages > defined in common. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4928) Use token request messages defined in hadoop common
[ https://issues.apache.org/jira/browse/MAPREDUCE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553286#comment-13553286 ] Siddharth Seth commented on MAPREDUCE-4928: --- +1. > Use token request messages defined in hadoop common > > > Key: MAPREDUCE-4928 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4928 > Project: Hadoop Map/Reduce > Issue Type: Improvement > Components: applicationmaster, security >Reporter: Suresh Srinivas >Assignee: Suresh Srinivas > Attachments: MR-4928.patch, MR-4928.patch, MR-4928.patch, > MR-4928.patch > > > MapReduce changes related to HADOOP-9192 to reuse the protobuf messages > defined in common. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4941) Use of org.apache.hadoop.mapred.lib.CombineFileRecordReader requires casting
[
https://issues.apache.org/jira/browse/MAPREDUCE-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553265#comment-13553265
]
Hadoop QA commented on MAPREDUCE-4941:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12564797/MAPREDUCE-4941.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 2
release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3237//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3237//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3237//console
This message is automatically generated.
> Use of org.apache.hadoop.mapred.lib.CombineFileRecordReader requires casting
>
>
> Key: MAPREDUCE-4941
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4941
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Affects Versions: 2.0.2-alpha, 0.23.5
>Reporter: Jason Lowe
>Assignee: Jason Lowe
>Priority: Minor
> Attachments: MAPREDUCE-4941.patch
>
>
> Unlike its counterpart in org.apache.hadoop.mapreduce.lib.input, the
> CombineFileRecordReader in mapred requires a user to cast to a RecordReader
> since the constructor specification says it must have the RecordReader
> class as a parameter. It should use {{Class>}}
> like its mapreduce counterpart to make it easier to use.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4941) Use of org.apache.hadoop.mapred.lib.CombineFileRecordReader requires casting
[
https://issues.apache.org/jira/browse/MAPREDUCE-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated MAPREDUCE-4941:
--
Attachment: MAPREDUCE-4941.patch
> Use of org.apache.hadoop.mapred.lib.CombineFileRecordReader requires casting
>
>
> Key: MAPREDUCE-4941
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4941
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Affects Versions: 2.0.2-alpha, 0.23.5
>Reporter: Jason Lowe
>Priority: Minor
> Attachments: MAPREDUCE-4941.patch
>
>
> Unlike its counterpart in org.apache.hadoop.mapreduce.lib.input, the
> CombineFileRecordReader in mapred requires a user to cast to a RecordReader
> since the constructor specification says it must have the RecordReader
> class as a parameter. It should use {{Class>}}
> like its mapreduce counterpart to make it easier to use.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4941) Use of org.apache.hadoop.mapred.lib.CombineFileRecordReader requires casting
[
https://issues.apache.org/jira/browse/MAPREDUCE-4941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated MAPREDUCE-4941:
--
Assignee: Jason Lowe
Target Version/s: 2.0.3-alpha, 0.23.6
Status: Patch Available (was: Open)
> Use of org.apache.hadoop.mapred.lib.CombineFileRecordReader requires casting
>
>
> Key: MAPREDUCE-4941
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4941
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Affects Versions: 0.23.5, 2.0.2-alpha
>Reporter: Jason Lowe
>Assignee: Jason Lowe
>Priority: Minor
> Attachments: MAPREDUCE-4941.patch
>
>
> Unlike its counterpart in org.apache.hadoop.mapreduce.lib.input, the
> CombineFileRecordReader in mapred requires a user to cast to a RecordReader
> since the constructor specification says it must have the RecordReader
> class as a parameter. It should use {{Class>}}
> like its mapreduce counterpart to make it easier to use.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-4941) Use of org.apache.hadoop.mapred.lib.CombineFileRecordReader requires casting
Jason Lowe created MAPREDUCE-4941:
-
Summary: Use of
org.apache.hadoop.mapred.lib.CombineFileRecordReader requires casting
Key: MAPREDUCE-4941
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4941
Project: Hadoop Map/Reduce
Issue Type: Bug
Affects Versions: 0.23.5, 2.0.2-alpha
Reporter: Jason Lowe
Priority: Minor
Unlike its counterpart in org.apache.hadoop.mapreduce.lib.input, the
CombineFileRecordReader in mapred requires a user to cast to a RecordReader
since the constructor specification says it must have the RecordReader
class as a parameter. It should use {{Class>}}
like its mapreduce counterpart to make it easier to use.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4808) Allow reduce-side merge to be pluggable
[
https://issues.apache.org/jira/browse/MAPREDUCE-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553076#comment-13553076
]
Chris Douglas commented on MAPREDUCE-4808:
--
[~tucu00]: that sounds reasonable; it should also simplify the API by
eliminating the {{mergeLocalFiles}} method.
> Allow reduce-side merge to be pluggable
> ---
>
> Key: MAPREDUCE-4808
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4808
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
>Affects Versions: 2.0.2-alpha
>Reporter: Arun C Murthy
>Assignee: Mariappan Asokan
> Fix For: 2.0.3-alpha
>
> Attachments: COMBO-mapreduce-4809-4812-4808.patch,
> mapreduce-4808.patch, mapreduce-4808.patch, mapreduce-4808.patch,
> mapreduce-4808.patch, mapreduce-4808.patch, MergeManagerPlugin.pdf
>
>
> Allow reduce-side merge to be pluggable for MAPREDUCE-2454
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4808) Allow reduce-side merge to be pluggable
[ https://issues.apache.org/jira/browse/MAPREDUCE-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553069#comment-13553069 ] Alejandro Abdelnur commented on MAPREDUCE-4808: --- Arun, Chris, Asokan, It seem the contention point here is adding the MergerManager as public API. How about the following alternative? * 1. Refactoring of the MapOutput into abstract class and introduce the Memory and Disk subclasses. * 2. Make the MergerManager pluggable in the Shuffle class via ReflectionUtils or a protected createMergeManager() method. * 3. Move the thread creation from the MergeManager constructor to an init() method. This would keep the MergerManager specific to the Shuffle implementation but it would allow alternate implementations to reuse parts of it. The only thing left would be how to handle the local case which currently is done by the Merger via a static method. > Allow reduce-side merge to be pluggable > --- > > Key: MAPREDUCE-4808 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4808 > Project: Hadoop Map/Reduce > Issue Type: New Feature >Affects Versions: 2.0.2-alpha >Reporter: Arun C Murthy >Assignee: Mariappan Asokan > Fix For: 2.0.3-alpha > > Attachments: COMBO-mapreduce-4809-4812-4808.patch, > mapreduce-4808.patch, mapreduce-4808.patch, mapreduce-4808.patch, > mapreduce-4808.patch, mapreduce-4808.patch, MergeManagerPlugin.pdf > > > Allow reduce-side merge to be pluggable for MAPREDUCE-2454 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4936) JobImpl uber checks for cpu are wrong
[
https://issues.apache.org/jira/browse/MAPREDUCE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553010#comment-13553010
]
Arun C Murthy commented on MAPREDUCE-4936:
--
My bad - I'm pretty sure these passed when I ran it initially. IAC, I'll fix
this. Thanks for pointing it out Daryn.
> JobImpl uber checks for cpu are wrong
> -
>
> Key: MAPREDUCE-4936
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4936
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
>Affects Versions: 3.0.0, 2.0.3-alpha
>Reporter: Daryn Sharp
>Assignee: Arun C Murthy
>Priority: Critical
>
> The cpu checks for uberizing have two issues:
> # the defaults are hardcoded instead of using the conf defaults
> # the comparison against the sys cpu size is using {{<}} instead of {{<=}}
> {code}
> boolean smallCpu =
> (
> Math.max(
> conf.getInt(MRJobConfig.MAP_CPU_VCORES, 1),
> conf.getInt(MRJobConfig.REDUCE_CPU_VCORES, 1)) <
> sysCPUSizeForUberSlot
> );
> {code}
> Everything is defaulting to 1, so uber cpu checks are now disabled causing
> {{TestUberAM}} to fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (MAPREDUCE-4936) JobImpl uber checks for cpu are wrong
[
https://issues.apache.org/jira/browse/MAPREDUCE-4936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy reassigned MAPREDUCE-4936:
Assignee: Arun C Murthy
> JobImpl uber checks for cpu are wrong
> -
>
> Key: MAPREDUCE-4936
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4936
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
>Affects Versions: 3.0.0, 2.0.3-alpha
>Reporter: Daryn Sharp
>Assignee: Arun C Murthy
>Priority: Critical
>
> The cpu checks for uberizing have two issues:
> # the defaults are hardcoded instead of using the conf defaults
> # the comparison against the sys cpu size is using {{<}} instead of {{<=}}
> {code}
> boolean smallCpu =
> (
> Math.max(
> conf.getInt(MRJobConfig.MAP_CPU_VCORES, 1),
> conf.getInt(MRJobConfig.REDUCE_CPU_VCORES, 1)) <
> sysCPUSizeForUberSlot
> );
> {code}
> Everything is defaulting to 1, so uber cpu checks are now disabled causing
> {{TestUberAM}} to fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-2817) MiniRMCluster hardcodes 'mapred.local.dir' configuration to 'build/test/mapred/local'
[
https://issues.apache.org/jira/browse/MAPREDUCE-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552920#comment-13552920
]
Hadoop QA commented on MAPREDUCE-2817:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12564739/MAPREDUCE-2817.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3236//console
This message is automatically generated.
> MiniRMCluster hardcodes 'mapred.local.dir' configuration to
> 'build/test/mapred/local'
> -
>
> Key: MAPREDUCE-2817
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2817
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
>Affects Versions: 0.20.2
> Environment: all
>Reporter: Alejandro Abdelnur
>Assignee: Robert Kanter
>Priority: Minor
> Attachments: MAPREDUCE-2817.patch, MAPREDUCE-2817.r1.diff
>
>
> The {{mapred.local.dir}} configuration property for the {{MiniMRCluster}} is
> forced to {{build/test/mapred/local}}
> This is inconvenient in different situations. For example:
> * When running multiple tests using {{MiniMRCluster}} is not possible to see
> the end state of the dir for a particular test
> * When using {{MiniMRCluster}} in another build system (i.e. Maven) that uses
> a different output directory (target instead build)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-2817) MiniRMCluster hardcodes 'mapred.local.dir' configuration to 'build/test/mapred/local'
[
https://issues.apache.org/jira/browse/MAPREDUCE-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated MAPREDUCE-2817:
-
Status: Patch Available (was: Reopened)
> MiniRMCluster hardcodes 'mapred.local.dir' configuration to
> 'build/test/mapred/local'
> -
>
> Key: MAPREDUCE-2817
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2817
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
>Affects Versions: 0.20.2
> Environment: all
>Reporter: Alejandro Abdelnur
>Assignee: Robert Kanter
>Priority: Minor
> Attachments: MAPREDUCE-2817.patch, MAPREDUCE-2817.r1.diff
>
>
> The {{mapred.local.dir}} configuration property for the {{MiniMRCluster}} is
> forced to {{build/test/mapred/local}}
> This is inconvenient in different situations. For example:
> * When running multiple tests using {{MiniMRCluster}} is not possible to see
> the end state of the dir for a particular test
> * When using {{MiniMRCluster}} in another build system (i.e. Maven) that uses
> a different output directory (target instead build)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-2817) MiniRMCluster hardcodes 'mapred.local.dir' configuration to 'build/test/mapred/local'
[
https://issues.apache.org/jira/browse/MAPREDUCE-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated MAPREDUCE-2817:
-
Attachment: MAPREDUCE-2817.patch
This patch is the same as Harsh's except that it reuses {{test.build.data}}
instead of adding a new one.
> MiniRMCluster hardcodes 'mapred.local.dir' configuration to
> 'build/test/mapred/local'
> -
>
> Key: MAPREDUCE-2817
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2817
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
>Affects Versions: 0.20.2
> Environment: all
>Reporter: Alejandro Abdelnur
>Assignee: Robert Kanter
>Priority: Minor
> Attachments: MAPREDUCE-2817.patch, MAPREDUCE-2817.r1.diff
>
>
> The {{mapred.local.dir}} configuration property for the {{MiniMRCluster}} is
> forced to {{build/test/mapred/local}}
> This is inconvenient in different situations. For example:
> * When running multiple tests using {{MiniMRCluster}} is not possible to see
> the end state of the dir for a particular test
> * When using {{MiniMRCluster}} in another build system (i.e. Maven) that uses
> a different output directory (target instead build)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (MAPREDUCE-2817) MiniRMCluster hardcodes 'mapred.local.dir' configuration to 'build/test/mapred/local'
[
https://issues.apache.org/jira/browse/MAPREDUCE-2817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter reopened MAPREDUCE-2817:
--
Assignee: Robert Kanter (was: Harsh J)
This actually would be useful to have; for example, tests that use
MiniMRCluster will write to {{build/test/mapred/local/jobTracker}}, and it
would be nice if we could override this.
> MiniRMCluster hardcodes 'mapred.local.dir' configuration to
> 'build/test/mapred/local'
> -
>
> Key: MAPREDUCE-2817
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2817
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
>Affects Versions: 0.20.2
> Environment: all
>Reporter: Alejandro Abdelnur
>Assignee: Robert Kanter
>Priority: Minor
> Attachments: MAPREDUCE-2817.r1.diff
>
>
> The {{mapred.local.dir}} configuration property for the {{MiniMRCluster}} is
> forced to {{build/test/mapred/local}}
> This is inconvenient in different situations. For example:
> * When running multiple tests using {{MiniMRCluster}} is not possible to see
> the end state of the dir for a particular test
> * When using {{MiniMRCluster}} in another build system (i.e. Maven) that uses
> a different output directory (target instead build)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (MAPREDUCE-4934) Maven RAT plugin is not checking all source files
[ https://issues.apache.org/jira/browse/MAPREDUCE-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Graves updated MAPREDUCE-4934: - Resolution: Fixed Fix Version/s: 0.23.6 2.0.3-alpha 3.0.0 Status: Resolved (was: Patch Available) > Maven RAT plugin is not checking all source files > - > > Key: MAPREDUCE-4934 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4934 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: build >Affects Versions: 2.0.2-alpha, 0.23.5 >Reporter: Thomas Graves >Assignee: Thomas Graves >Priority: Critical > Fix For: 3.0.0, 2.0.3-alpha, 0.23.6 > > Attachments: MAPREDUCE-4934-branch-0.23.patch, > MAPREDUCE-4934-branch-0.23.patch, MAPREDUCE-4934.patch, MAPREDUCE-4934.patch > > > mapreduce side of HADOOP-9097 > Running 'mvn apache-rat:check' passes, but running RAT by hand (by > downloading the JAR) produces some warnings for Java files, amongst others. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4520) Add experimental support for MR AM to schedule CPUs along-with memory
[ https://issues.apache.org/jira/browse/MAPREDUCE-4520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552765#comment-13552765 ] Tom White commented on MAPREDUCE-4520: -- Arun, even "trivial" code changes require a review before being committed. The change breaks existing unit tests. Please see MAPREDUCE-4936. Also, since this is adding a new feature it should have new tests (e.g. something that exercises the new mapreduce.map.cpu.vcores and mapreduce.reduce.cpu.vcores properties). > Add experimental support for MR AM to schedule CPUs along-with memory > - > > Key: MAPREDUCE-4520 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4520 > Project: Hadoop Map/Reduce > Issue Type: New Feature >Reporter: Arun C Murthy >Assignee: Arun C Murthy > Fix For: 2.0.3-alpha > > Attachments: MAPREDUCE-4520.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MAPREDUCE-4940) division by zero in getLocalPathForWrite()
[
https://issues.apache.org/jira/browse/MAPREDUCE-4940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved MAPREDUCE-4940.
Resolution: Duplicate
> division by zero in getLocalPathForWrite()
> --
>
> Key: MAPREDUCE-4940
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4940
> Project: Hadoop Map/Reduce
> Issue Type: Bug
>Reporter: Ted Yu
>
> see
> https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/345/testReport/org.apache.hadoop.hbase.mapreduce/TestImportExport/testSimpleCase/
> {code}
> 2013-01-12 11:53:52,809 WARN [AsyncDispatcher event handler]
> resourcemanager.RMAuditLogger(255): USER=jenkinsOPERATION=Application
> Finished - Failed TARGET=RMAppManager RESULT=FAILURE DESCRIPTION=App
> failed with state: FAILED PERMISSIONS=Application
> application_1357991604658_0002 failed 1 times due to AM Container for
> appattempt_1357991604658_0002_01 exited with exitCode: -1000 due to:
> java.lang.ArithmeticException: / by zero
> at
> org.apache.hadoop.fs.LocalDirAllocator$AllocatorPerContext.getLocalPathForWrite(LocalDirAllocator.java:368)
> at
> org.apache.hadoop.fs.LocalDirAllocator.getLocalPathForWrite(LocalDirAllocator.java:150)
> at
> org.apache.hadoop.fs.LocalDirAllocator.getLocalPathForWrite(LocalDirAllocator.java:131)
> at
> org.apache.hadoop.fs.LocalDirAllocator.getLocalPathForWrite(LocalDirAllocator.java:115)
> at
> org.apache.hadoop.yarn.server.nodemanager.LocalDirsHandlerService.getLocalPathForWrite(LocalDirsHandlerService.java:279)
> at
> org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService$LocalizerRunner.run(ResourceLocalizationService.java:851)
> .Failing this attempt.. Failing the application.
> APPID=application_1357991604658_0002
> {code}
> Here is related code:
> {code}
> // Keep rolling the wheel till we get a valid path
> Random r = new java.util.Random();
> while (numDirsSearched < numDirs && returnPath == null) {
> long randomPosition = Math.abs(r.nextLong()) % totalAvailable;
> {code}
> My guess is that totalAvailable was 0, meaning dirDF was empty.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MAPREDUCE-4940) division by zero in getLocalPathForWrite()
Ted Yu created MAPREDUCE-4940:
-
Summary: division by zero in getLocalPathForWrite()
Key: MAPREDUCE-4940
URL: https://issues.apache.org/jira/browse/MAPREDUCE-4940
Project: Hadoop Map/Reduce
Issue Type: Bug
Reporter: Ted Yu
see
https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/345/testReport/org.apache.hadoop.hbase.mapreduce/TestImportExport/testSimpleCase/
{code}
2013-01-12 11:53:52,809 WARN [AsyncDispatcher event handler]
resourcemanager.RMAuditLogger(255): USER=jenkins OPERATION=Application
Finished - Failed TARGET=RMAppManager RESULT=FAILURE DESCRIPTION=App
failed with state: FAILED PERMISSIONS=Application
application_1357991604658_0002 failed 1 times due to AM Container for
appattempt_1357991604658_0002_01 exited with exitCode: -1000 due to:
java.lang.ArithmeticException: / by zero
at
org.apache.hadoop.fs.LocalDirAllocator$AllocatorPerContext.getLocalPathForWrite(LocalDirAllocator.java:368)
at
org.apache.hadoop.fs.LocalDirAllocator.getLocalPathForWrite(LocalDirAllocator.java:150)
at
org.apache.hadoop.fs.LocalDirAllocator.getLocalPathForWrite(LocalDirAllocator.java:131)
at
org.apache.hadoop.fs.LocalDirAllocator.getLocalPathForWrite(LocalDirAllocator.java:115)
at
org.apache.hadoop.yarn.server.nodemanager.LocalDirsHandlerService.getLocalPathForWrite(LocalDirsHandlerService.java:279)
at
org.apache.hadoop.yarn.server.nodemanager.containermanager.localizer.ResourceLocalizationService$LocalizerRunner.run(ResourceLocalizationService.java:851)
.Failing this attempt.. Failing the application.
APPID=application_1357991604658_0002
{code}
Here is related code:
{code}
// Keep rolling the wheel till we get a valid path
Random r = new java.util.Random();
while (numDirsSearched < numDirs && returnPath == null) {
long randomPosition = Math.abs(r.nextLong()) % totalAvailable;
{code}
My guess is that totalAvailable was 0, meaning dirDF was empty.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MAPREDUCE-4934) Maven RAT plugin is not checking all source files
[ https://issues.apache.org/jira/browse/MAPREDUCE-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13552696#comment-13552696 ] Hudson commented on MAPREDUCE-4934: --- Integrated in Hadoop-trunk-Commit #3224 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/3224/]) MAPREDUCE-4934. Maven RAT plugin is not checking all source files (tgraves) (Revision 1432932) Result = SUCCESS tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1432932 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/conf/mapred-site.xml.template * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/resources/META-INF/services/org.apache.hadoop.security.SecurityInfo * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/launcher/TestContainerLauncherImpl.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/local/TestLocalContainerAllocator.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/resources/META-INF/services/org.apache.hadoop.security.token.TokenIdentifier * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/resources/META-INF/services/org.apache.hadoop.security.token.TokenRenewer * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/META-INF/services/org.apache.hadoop.security.token.TokenIdentifier * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/META-INF/services/org.apache.hadoop.security.token.TokenRenewer * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/pom.xml * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/test/java/org/apache/hadoop/mapreduce/v2/hs/MockHistoryJobs.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/test/java/org/apache/hadoop/mapreduce/v2/hs/TestJobHistoryEntities.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/pom.xml * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/main/resources/META-INF/services/org.apache.hadoop.security.SecurityInfo * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/pom.xml * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/test/java/org/apache/hadoop/examples/TestWordStats.java * /hadoop/common/trunk/hadoop-mapreduce-project/pom.xml > Maven RAT plugin is not checking all source files > - > > Key: MAPREDUCE-4934 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-4934 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: build >Affects Versions: 2.0.2-alpha, 0.23.5 >Reporter: Thomas Graves >Assignee: Thomas Graves >Priority: Critical > Attachments: MAPREDUCE-4934-branch-0.23.patch, > MAPREDUCE-4934-branch-0.23.patch, MAPREDUCE-4934.patch, MAPREDUCE-4934.patch > > > mapreduce side of HADOOP-9097 > Running 'mvn apache-rat:check' passes, but running RAT by hand (by > downloading the JAR) produces some warnings for Java files, amongst others. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
