hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashutosh Chauhan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-3537) release locks at the end of move tasks
Date Fri, 18 Jan 2013 13:36:14 GMT

    [ https://issues.apache.org/jira/browse/HIVE-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13557206#comment-13557206
] 

Ashutosh Chauhan commented on HIVE-3537:
----------------------------------------

Looks good. Running tests. Will commit if tests pass.
                
> release locks at the end of move tasks
> --------------------------------------
>
>                 Key: HIVE-3537
>                 URL: https://issues.apache.org/jira/browse/HIVE-3537
>             Project: Hive
>          Issue Type: Bug
>          Components: Locking, Query Processor
>            Reporter: Namit Jain
>            Assignee: Namit Jain
>         Attachments: hive.3537.10.patch, hive.3537.1.patch, hive.3537.2.patch, hive.3537.3.patch,
hive.3537.4.patch, hive.3537.5.patch, hive.3537.6.patch, hive.3537.7.patch, hive.3537.8.patch,
hive.3537.9.patch
>
>
> Look at HIVE-3106 for details.
> In order to make sure that concurrency is not an issue for multi-table 
> inserts, the current option is to introduce a dependency task, which thereby
> delays the creation of all partitions. It would be desirable to release the
> locks for the outputs as soon as the move task is completed. That way, for
> multi-table inserts, the concurrency can be enabled without delaying any 
> table.
> Currently, the movetask contains a input/output, but they do not seem to be
> populated correctly.

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

Mime
View raw message