[
https://issues.apache.org/jira/browse/SQOOP-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13632064#comment-13632064
]
Hudson commented on SQOOP-967:
------------------------------
Integrated in Sqoop2-hadoop200 #266 (See
[https://builds.apache.org/job/Sqoop2-hadoop200/266/])
SQOOP-967: Sqoop2: Introduce dummy configuration key to easily identify
Sqoop2 job (Revision 722e6480ea5fb1d7f7b221d478e68ff239583c80)
Result = SUCCESS
kathleen :
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=722e6480ea5fb1d7f7b221d478e68ff239583c80
Files :
*
submission/mapreduce/src/main/java/org/apache/sqoop/submission/mapreduce/Constants.java
*
submission/mapreduce/src/main/java/org/apache/sqoop/submission/mapreduce/MapreduceSubmissionEngine.java
> Sqoop2: Introduce dummy configuration key to easily identify Sqoop2 job
> -----------------------------------------------------------------------
>
> Key: SQOOP-967
> URL: https://issues.apache.org/jira/browse/SQOOP-967
> Project: Sqoop
> Issue Type: Improvement
> Affects Versions: 1.99.1
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Priority: Trivial
> Fix For: 1.99.2
>
> Attachments: bugSQOOP-967.patch
>
>
> It would be useful for tools that are introspecting all Hadoop running jobs
> to provide very simple way how to identify Sqoop2 job. I would suggest to
> simply put very simple configuration property ("sqoop.job"?) into the
> configuration object.
--
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
