You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Teddy Choi (Jira)" <ji...@apache.org> on 2022/09/26 05:18:00 UTC

[jira] [Updated] (HIVE-26555) Read-only mode for Hive database

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

Teddy Choi updated HIVE-26555:
------------------------------
    Summary: Read-only mode for Hive database  (was: Read-only mode)

> 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: 0.5h
>  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. Design
> 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.
> Allowed operations prefixes
>  * EXPLAIN
>  * USE(or SWITCHDATABASE)
>  * REPLDUMP
>  * REPLSTATUS
>  * EXPORT
>  * KILL_QUERY
>  * DESC
>  * SHOW
> 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)