[
https://issues.apache.org/jira/browse/HIVE-18526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16343797#comment-16343797
]
Vihang Karajgaonkar commented on HIVE-18526:
--------------------------------------------
Okay, looks like [~anishek] has raised a good point on this patch on
HIVE-16886. Copying it here for reference:
{quote}[http://www.datanucleus.org/products/accessplatform_4_1/jdo/transactions.html]
{quote}
{quote}By default DataNucleus does not currently lock the objects fetched with
pessimistic locking, but you can configure this behaviour for RDBMS datastores
by setting the persistence property datanucleus.SerializeRead to true. This
will result in all "SELECT ... FROM ..." statements being changed to be "SELECT
... FROM ... FOR UPDATE". This will be applied only where the underlying RDBMS
supports the "FOR UPDATE" syntax.
{quote}
{quote}for SQLServer this will not work since the syntax is different. the code
shows us using datanuclues 4.1 version btw.
{quote}
This patch may not work with SQL Server as suggested above.
Hi [~akolb] can you investigate if we can backport the original patch of
HIVE-16886 to branch-2. The patch you attached is a lot simpler but I think
since it may not work with MSSQL we will still have a problem. Also, I think it
is a good idea to keep branch-2 and master similar as far as individual patches
are concerned. Thanks!
> Backport HIVE-16886 to Hive 2
> -----------------------------
>
> Key: HIVE-18526
> URL: https://issues.apache.org/jira/browse/HIVE-18526
> Project: Hive
> Issue Type: Sub-task
> Components: Hive
> Affects Versions: 2.3.3
> Reporter: Alexander Kolbasov
> Assignee: Alexander Kolbasov
> Priority: Major
> Attachments: HIVE-18526.01-branch-2.patch,
> HIVE-18526.02-branch-2.patch
>
>
> The fix for HIVE-16886 isn't in Hive 2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
