[jira] [Commented] (MAPREDUCE-5374) CombineFileRecordReader does not set map.input.* configuration parameters for first file read
[
https://issues.apache.org/jira/browse/MAPREDUCE-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14525375#comment-14525375
]
Hadoop QA commented on MAPREDUCE-5374:
--
\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch | 14m 33s | Pre-patch trunk compilation is
healthy. |
| {color:green}+1{color} | @author | 0m 0s | The patch does not contain any
@author tags. |
| {color:red}-1{color} | tests included | 0m 0s | 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{color} | javac | 7m 32s | There were no new javac warning
messages. |
| {color:green}+1{color} | javadoc | 9m 31s | There were no new javadoc
warning messages. |
| {color:green}+1{color} | release audit | 0m 21s | The applied patch does
not increase the total number of release audit warnings. |
| {color:red}-1{color} | checkstyle | 0m 45s | The applied patch generated 2
new checkstyle issues (total was 17, now 19). |
| {color:green}+1{color} | whitespace | 0m 0s | The patch has no lines that
end in whitespace. |
| {color:green}+1{color} | install | 1m 33s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse | 0m 33s | The patch built with
eclipse:eclipse. |
| {color:green}+1{color} | findbugs | 1m 14s | The patch does not introduce
any new Findbugs (version 2.0.3) warnings. |
| {color:green}+1{color} | mapreduce tests | 1m 34s | Tests passed in
hadoop-mapreduce-client-core. |
| | | 37m 39s | |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL |
http://issues.apache.org/jira/secure/attachment/12590890/MAPREDUCE-5374.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| checkstyle |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5592/artifact/patchprocess/diffcheckstylehadoop-mapreduce-client-core.txt
|
| hadoop-mapreduce-client-core test log |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5592/artifact/patchprocess/testrun_hadoop-mapreduce-client-core.txt
|
| Test Results |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5592/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf901.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP
PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
| Console output |
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/5592/console |
This message was automatically generated.
CombineFileRecordReader does not set map.input.* configuration parameters
for first file read
---
Key: MAPREDUCE-5374
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5374
Project: Hadoop Map/Reduce
Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Dave Beech
Assignee: Dave Beech
Attachments: MAPREDUCE-5374.patch, MAPREDUCE-5374.patch
The CombineFileRecordReader operates on splits consisting of multiple files.
Each time a new record reader is initialised for a chunk, certain
parameters are supposed to be set on the configuration object
(map.input.file, map.input.start and map.input.length)
However, the first reader is initialised in a different way to subsequent
ones (i.e. initialize is called by the MapTask directly rather than from
inside the record reader class). Because of this, these config parameters are
not set properly and are returned as null when you access them from inside a
mapper.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MAPREDUCE-5374) CombineFileRecordReader does not set map.input.* configuration parameters for first file read
[
https://issues.apache.org/jira/browse/MAPREDUCE-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700057#comment-13700057
]
Hadoop QA commented on MAPREDUCE-5374:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12590884/MAPREDUCE-5374.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/3829//console
This message is automatically generated.
CombineFileRecordReader does not set map.input.* configuration parameters
for first file read
---
Key: MAPREDUCE-5374
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5374
Project: Hadoop Map/Reduce
Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Dave Beech
Assignee: Dave Beech
Attachments: MAPREDUCE-5374.patch
The CombineFileRecordReader operates on splits consisting of multiple files.
Each time a new record reader is initialised for a chunk, certain
parameters are supposed to be set on the configuration object
(map.input.file, map.input.start and map.input.length)
However, the first reader is initialised in a different way to subsequent
ones (i.e. initialize is called by the MapTask directly rather than from
inside the record reader class). Because of this, these config parameters are
not set properly and are returned as null when you access them from inside a
mapper.
--
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-5374) CombineFileRecordReader does not set map.input.* configuration parameters for first file read
[
https://issues.apache.org/jira/browse/MAPREDUCE-5374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700070#comment-13700070
]
Hadoop QA commented on MAPREDUCE-5374:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12590890/MAPREDUCE-5374.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:green}+1 release audit{color}. The applied patch does not increase
the total number of 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/3831//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3831//console
This message is automatically generated.
CombineFileRecordReader does not set map.input.* configuration parameters
for first file read
---
Key: MAPREDUCE-5374
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5374
Project: Hadoop Map/Reduce
Issue Type: Bug
Affects Versions: 1.2.0
Reporter: Dave Beech
Assignee: Dave Beech
Attachments: MAPREDUCE-5374.patch, MAPREDUCE-5374.patch
The CombineFileRecordReader operates on splits consisting of multiple files.
Each time a new record reader is initialised for a chunk, certain
parameters are supposed to be set on the configuration object
(map.input.file, map.input.start and map.input.length)
However, the first reader is initialised in a different way to subsequent
ones (i.e. initialize is called by the MapTask directly rather than from
inside the record reader class). Because of this, these config parameters are
not set properly and are returned as null when you access them from inside a
mapper.
--
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
