You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/05/23 11:20:00 UTC
[jira] [Work logged] (HIVE-26258) Provide an option for strict locking of external tables
[ https://issues.apache.org/jira/browse/HIVE-26258?focusedWorklogId=773428&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-773428 ]
ASF GitHub Bot logged work on HIVE-26258:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 23/May/22 11:19
Start Date: 23/May/22 11:19
Worklog Time Spent: 10m
Work Description: pvary opened a new pull request, #3313:
URL: https://github.com/apache/hive/pull/3313
### What changes were proposed in this pull request?
Adds `hive.txn.strict.ext.locking.mode`: In strict mode external resources use standard R/W lock semantics,
e.g. INSERT will acquire exclusive lock, SELECT will acquire shared lock based on hive.txn.nonacid.read.locks.
In nonstrict mode no locks are acquired for external resources.
### Why are the changes needed?
For backward compatibility
### Does this PR introduce _any_ user-facing change?
Adding a new feature, when turned off, no change is expected. The feature is turned off by default.
### How was this patch tested?
Added unit tests.
Issue Time Tracking
-------------------
Worklog Id: (was: 773428)
Remaining Estimate: 0h
Time Spent: 10m
> Provide an option for strict locking of external tables
> -------------------------------------------------------
>
> Key: HIVE-26258
> URL: https://issues.apache.org/jira/browse/HIVE-26258
> Project: Hive
> Issue Type: Improvement
> Reporter: Peter Vary
> Assignee: Peter Vary
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> During migration to Hive 3 the MANAGED tables are migrated to EXTERNAL tables.
> To provide backward compatibility we need an option to keep the original strict locking for these external tables.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)