Return-Path: Delivered-To: apmail-hadoop-hive-dev-archive@minotaur.apache.org Received: (qmail 6881 invoked from network); 3 May 2010 20:54:20 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 May 2010 20:54:20 -0000 Received: (qmail 5918 invoked by uid 500); 3 May 2010 20:54:20 -0000 Delivered-To: apmail-hadoop-hive-dev-archive@hadoop.apache.org Received: (qmail 5896 invoked by uid 500); 3 May 2010 20:54:20 -0000 Mailing-List: contact hive-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hive-dev@hadoop.apache.org Delivered-To: mailing list hive-dev@hadoop.apache.org Received: (qmail 5888 invoked by uid 99); 3 May 2010 20:54:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 20:54:19 +0000 X-ASF-Spam-Status: No, hits=-1381.8 required=10.0 tests=ALL_TRUSTED,AWL X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 20:54:18 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o43KrwdE001654 for ; Mon, 3 May 2010 20:53:58 GMT Message-ID: <22331899.22261272920038428.JavaMail.jira@thor> Date: Mon, 3 May 2010 16:53:58 -0400 (EDT) From: "Namit Jain (JIRA)" To: hive-dev@hadoop.apache.org Subject: [jira] Assigned: (HIVE-1293) Concurreny Model for Hive In-Reply-To: <1912839159.1091270683576781.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HIVE-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Namit Jain reassigned HIVE-1293: -------------------------------- Assignee: Namit Jain > Concurreny Model for Hive > ------------------------- > > Key: HIVE-1293 > URL: https://issues.apache.org/jira/browse/HIVE-1293 > Project: Hadoop Hive > Issue Type: New Feature > Components: Query Processor > Reporter: Namit Jain > Assignee: Namit Jain > > Concurrency model for Hive: > Currently, hive does not provide a good concurrency model. The only guanrantee provided in case of concurrent readers and writers is that > reader will not see partial data from the old version (before the write) and partial data from the new version (after the write). > This has come across as a big problem, specially for background processes performing maintenance operations. > The following possible solutions come to mind. > 1. Locks: Acquire read/write locks - they can be acquired at the beginning of the query or the write locks can be delayed till move > task (when the directory is actually moved). Care needs to be taken for deadlocks. > 2. Versioning: The writer can create a new version if the current version is being read. Note that, it is not equivalent to snapshots, > the old version can only be accessed by the current readers, and will be deleted when all of them have finished. > Comments. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.