You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Namit Jain (JIRA)" <ji...@apache.org> on 2009/09/14 21:04:57 UTC

[jira] Created: (HIVE-829) no atomicity for a reader/writer for a job

no atomicity for a reader/writer for a job
------------------------------------------

                 Key: HIVE-829
                 URL: https://issues.apache.org/jira/browse/HIVE-829
             Project: Hadoop Hive
          Issue Type: New Feature
          Components: Query Processor
            Reporter: Namit Jain


Hive currently does not provide any atomicity for a reader/writer.

So, if a reader/writer is running concurrently, the reader may randomly die or even see partial results. 
Some kind of synchronization mechanisms (lease, lock in metastore/somewhere else) are needed to manage the above.

This also applies to multiple writers (say multiple load into...)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (HIVE-829) no atomicity for a reader/writer for a job

Posted by "Namit Jain (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HIVE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Namit Jain resolved HIVE-829.
-----------------------------

    Resolution: Duplicate

Duplicate of https://issues.apache.org/jira/browse/HIVE-1293

> no atomicity for a reader/writer for a job
> ------------------------------------------
>
>                 Key: HIVE-829
>                 URL: https://issues.apache.org/jira/browse/HIVE-829
>             Project: Hadoop Hive
>          Issue Type: New Feature
>          Components: Query Processor
>            Reporter: Namit Jain
>
> Hive currently does not provide any atomicity for a reader/writer.
> So, if a reader/writer is running concurrently, the reader may randomly die or even see partial results. 
> Some kind of synchronization mechanisms (lease, lock in metastore/somewhere else) are needed to manage the above.
> This also applies to multiple writers (say multiple load into...)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.