[
https://issues.apache.org/jira/browse/HIVE-26555?focusedWorklogId=834260&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-834260
]
ASF GitHub Bot logged work on HIVE-26555:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Dec/22 00:18
Start Date: 17/Dec/22 00:18
Worklog Time Spent: 10m
Work Description: github-actions[bot] commented on PR #3614:
URL: https://github.com/apache/hive/pull/3614#issuecomment-1355861893
This pull request has been automatically marked as stale because it has not
had recent activity. It will be closed if no further activity occurs.
Feel free to reach out on the [email protected] list if the patch is in
need of reviews.
Issue Time Tracking
-------------------
Worklog Id: (was: 834260)
Time Spent: 1h 10m (was: 1h)
> Read-only mode for Hive database
> --------------------------------
>
> Key: HIVE-26555
> URL: https://issues.apache.org/jira/browse/HIVE-26555
> Project: Hive
> Issue Type: New Feature
> Reporter: Teddy Choi
> Assignee: Teddy Choi
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> h1. Purpose
> In failover/fail-back scenarios, a Hive database needs to be read-only, while
> other one is writable to keep a single source of truth.
> h1. User-Facing Changes
> Yes. EnforceReadOnlyDatabaseHook class implements ExecuteWithHookContext
> interface. hive.exec.pre.hooks needs to have the class name to initiate an
> instance. The "readonly" database property can be configured to turn it on
> and off.
> h2. Allowed read operations
> All read operations without any data/metadata change are allowed.
> * EXPLAIN
> * USE(or SWITCHDATABASE)
> * REPLDUMP
> * REPLSTATUS
> * EXPORT
> * KILL_QUERY
> * DESC prefix
> * SHOW prefix
> * QUERY with SELECT or EXPLAIN. INSERT, DELETE, UPDATE are disallowed.
> h2. Allowed write operations
> Most of write operations that change data/metadata are disallowed. There are
> few allowed exceptions. The first one is alter database to make a database
> writable. The second one is replication load to load a dumped database.
> * ALTER DATABASE db_name SET DBPROPERTIES without "readonly"="true".
> * REPLLOAD
> h1. Tests
> * read_only_hook.q: USE, SHOW, DESC, DESCRIBE, EXPLAIN, SELECT
> * read_only_delete.q
> * read_only_insert.q
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
