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 2013/06/03 18:33:20 UTC

[jira] [Updated] (SQOOP-1065) Sqoop2: Remove special lock object in FrameworkManager

     [ https://issues.apache.org/jira/browse/SQOOP-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jarek Jarcec Cecho updated SQOOP-1065:
--------------------------------------

    Attachment: bugSQOOP-1065.patch
    
> Sqoop2: Remove special lock object in FrameworkManager
> ------------------------------------------------------
>
>                 Key: SQOOP-1065
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1065
>             Project: Sqoop
>          Issue Type: Improvement
>    Affects Versions: 1.99.2
>            Reporter: Jarek Jarcec Cecho
>            Assignee: Jarek Jarcec Cecho
>            Priority: Trivial
>             Fix For: 1.99.3
>
>         Attachments: bugSQOOP-1065.patch
>
>
> {{FrameworkManager}} is currently using special lock object to ensure that we are not running one job multiple times. I think that using a special object is redundant as we can use any other immutable object like the class itself.

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