You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Jarek Jarcec Cecho (JIRA)" <ji...@apache.org> on 2015/03/19 19:52:40 UTC

[jira] [Created] (SQOOP-2239) Sqoop2: Remove Repository.updateSubmission() call from Mapreduce submission engine

Jarek Jarcec Cecho created SQOOP-2239:
-----------------------------------------

             Summary: 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


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)