Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 23 May 2014 22:20:01 +0000 (UTC)
From: "Alan Gates (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12710172.1398291932923.11869.1400883601849@arcas>
In-Reply-To: <JIRA.12710172.1398291932923@arcas>
References: <JIRA.12710172.1398291932923@arcas>
Subject: [jira] [Updated] (HIVE-6967) Hive transaction manager fails when
 SQLServer is used as an RDBMS
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-6967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Gates updated HIVE-6967:
-----------------------------

    Attachment: HIVE-6967.patch

A patch that changes the transaction manager to use serializable isolation instead of select for update.  Each operation is allowed to select whether it wants serializable (which ones that used to use select for update use) or read committed (for other operations).

> Hive transaction manager fails when SQLServer is used as an RDBMS
> -----------------------------------------------------------------
>
>                 Key: HIVE-6967
>                 URL: https://issues.apache.org/jira/browse/HIVE-6967
>             Project: Hive
>          Issue Type: Bug
>          Components: Locking
>    Affects Versions: 0.13.0
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>         Attachments: HIVE-6967.patch
>
>
> When using SQLServer as an RDBMS for the metastore, any transaction or DbLockMgr operations fail with:
> {code}
> MetaException(message:Unable to select from transaction database com.microsoft.sqlserver.jdbc.SQLServerException: Line 1: FOR UPDATE clause allowed only for DECLARE CURSOR.
> {code}
> The issue is that SQLServer does not support the FOR UPDATE clause in SELECT.


--
This message was sent by Atlassian JIRA
(v6.2#6252)