You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Hari Shreedharan (JIRA)" <ji...@apache.org> on 2012/11/15 01:14:12 UTC
[jira] [Created] (SQOOP-702) OutputLoadExecutor consumer thread
should not be daemon
Hari Shreedharan created SQOOP-702:
--------------------------------------
Summary: OutputLoadExecutor consumer thread should not be daemon
Key: SQOOP-702
URL: https://issues.apache.org/jira/browse/SQOOP-702
Project: Sqoop
Issue Type: Bug
Affects Versions: 2.0.0
Reporter: Hari Shreedharan
Fix For: 2.0.0
Consumer thread calls loader.run() which might actually have to do some clean up if it is being terminated. Being a daemon thread, there is no guarantee any actual cleanup (even in finally blocks) will actually be called.
--
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
[jira] [Updated] (SQOOP-702) OutputLoadExecutor consumer thread
should not be daemon
Posted by "Hari Shreedharan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Shreedharan updated SQOOP-702:
-----------------------------------
Attachment: SQOOP-702.patch
Rb does not let me submit this yet, since it cannot see the last commit I guess.
> OutputLoadExecutor consumer thread should not be daemon
> -------------------------------------------------------
>
> Key: SQOOP-702
> URL: https://issues.apache.org/jira/browse/SQOOP-702
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Hari Shreedharan
> Fix For: 2.0.0
>
> Attachments: SQOOP-702.patch
>
>
> Consumer thread calls loader.run() which might actually have to do some clean up if it is being terminated. Being a daemon thread, there is no guarantee any actual cleanup (even in finally blocks) will actually be called.
--
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
[jira] [Updated] (SQOOP-702) Refactor OutputLoadExecutor
Posted by "Hari Shreedharan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Shreedharan updated SQOOP-702:
-----------------------------------
Summary: Refactor OutputLoadExecutor (was: OutputLoadExecutor consumer thread should not be daemon)
> Refactor OutputLoadExecutor
> ---------------------------
>
> Key: SQOOP-702
> URL: https://issues.apache.org/jira/browse/SQOOP-702
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Hari Shreedharan
> Assignee: Hari Shreedharan
> Fix For: 2.0.0
>
> Attachments: SQOOP-702.patch
>
>
> Consumer thread calls loader.run() which might actually have to do some clean up if it is being terminated. Being a daemon thread, there is no guarantee any actual cleanup (even in finally blocks) will actually be called.
> Additional refactoring is needed in this class.
--
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
[jira] [Updated] (SQOOP-702) OutputLoadExecutor consumer thread
should not be daemon
Posted by "Hari Shreedharan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Shreedharan updated SQOOP-702:
-----------------------------------
Description:
Consumer thread calls loader.run() which might actually have to do some clean up if it is being terminated. Being a daemon thread, there is no guarantee any actual cleanup (even in finally blocks) will actually be called.
Additional refactoring is needed in this class.
was:Consumer thread calls loader.run() which might actually have to do some clean up if it is being terminated. Being a daemon thread, there is no guarantee any actual cleanup (even in finally blocks) will actually be called.
Assignee: Hari Shreedharan
> OutputLoadExecutor consumer thread should not be daemon
> -------------------------------------------------------
>
> Key: SQOOP-702
> URL: https://issues.apache.org/jira/browse/SQOOP-702
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Hari Shreedharan
> Assignee: Hari Shreedharan
> Fix For: 2.0.0
>
> Attachments: SQOOP-702.patch
>
>
> Consumer thread calls loader.run() which might actually have to do some clean up if it is being terminated. Being a daemon thread, there is no guarantee any actual cleanup (even in finally blocks) will actually be called.
> Additional refactoring is needed in this class.
--
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
[jira] [Updated] (SQOOP-702) Refactor OutputLoadExecutor
Posted by "Hari Shreedharan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SQOOP-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Shreedharan updated SQOOP-702:
-----------------------------------
Attachment: SQOOP-702-1.patch
Added some javadoc to the new method and also rethrowing the same exception if it is a SqoopException
> Refactor OutputLoadExecutor
> ---------------------------
>
> Key: SQOOP-702
> URL: https://issues.apache.org/jira/browse/SQOOP-702
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 2.0.0
> Reporter: Hari Shreedharan
> Assignee: Hari Shreedharan
> Fix For: 2.0.0
>
> Attachments: SQOOP-702-1.patch, SQOOP-702.patch
>
>
> Consumer thread calls loader.run() which might actually have to do some clean up if it is being terminated. Being a daemon thread, there is no guarantee any actual cleanup (even in finally blocks) will actually be called.
> Additional refactoring is needed in this class.
--
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