sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1065) Sqoop2: Remove special lock object in FrameworkManager
Date Sat, 22 Jun 2013 19:22:20 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691226#comment-13691226

ASF subversion and git services commented on SQOOP-1065:

Commit 05bd42e1840aa8d58034ab4eab1c92e1c1e47db1 in branch refs/heads/sqoop2 from [~nrv]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=05bd42e ]

SQOOP-1065: Sqoop2: Remove special lock object in FrameworkManager

(Jarek Jarcec Cecho via Venkat Ranganathan)

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

View raw message