[
https://issues.apache.org/jira/browse/SQOOP-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548961#comment-13548961
]
Hudson commented on SQOOP-821:
------------------------------
Integrated in Sqoop-ant-jdk-1.6-hadoop200 #485 (See
[https://builds.apache.org/job/Sqoop-ant-jdk-1.6-hadoop200/485/])
SQOOP-821: Hadoop has changed logic for job id in LocalJobRunner that
(Revision fea72de6e6f61f5849d991b385009e730a3d0694)
Result = SUCCESS
cheolsoo :
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=fea72de6e6f61f5849d991b385009e730a3d0694
Files :
* src/test/com/cloudera/sqoop/testutil/LobAvroImportTestCase.java
> Hadoop has changed logic for job id in LocalJobRunner that breaks Lob* tests
> ----------------------------------------------------------------------------
>
> Key: SQOOP-821
> URL: https://issues.apache.org/jira/browse/SQOOP-821
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.2
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Priority: Blocker
> Fix For: 1.4.3
>
> Attachments: MAPRED.patch
>
>
> I've noticed that MAPREDUCE-4278 got committed. This JIRA changed the logic
> of generating job id in LocalJobRunner from job_local_000 to
> job_local[randid]_000. As we're directly depending on the job ID name in one
> of our third party tests, we need to address this change.
--
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