[
https://issues.apache.org/jira/browse/SQOOP-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381139#comment-14381139
]
Hudson commented on SQOOP-2239:
-------------------------------
SUCCESS: Integrated in Sqoop2-hadoop200 #802 (See
[https://builds.apache.org/job/Sqoop2-hadoop200/802/])
SQOOP-2239: Sqoop2: Remove Repository.updateSubmission() call from Mapreduce
submission engine (abe:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=be74759e7844bc9de63b2583b6c3c72488803aa8)
*
submission/mapreduce/src/main/java/org/apache/sqoop/submission/mapreduce/MapreduceSubmissionEngine.java
* core/src/main/java/org/apache/sqoop/driver/JobManager.java
> Sqoop2: Remove Repository.updateSubmission() call from Mapreduce submission
> engine
> ----------------------------------------------------------------------------------
>
> Key: SQOOP-2239
> URL: https://issues.apache.org/jira/browse/SQOOP-2239
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.5
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.6
>
> Attachments: SQOOP-2239.patch
>
>
> Current mapreduce submission engine is updating repository when getting
> latest information about submission. This is unfortunate because it's
> breaking encapsulation - submission engine should be responsible only for
> updating the submission itself not to also persist it's state in repository.
> That is responsibility of the core JobManager itself. This way we will also
> ensure that we will persist the updated submission regardless what submission
> engine will be used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
