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/23 00:11:00 UTC

[jira] [Work started] (HIVE-26555) Read-only mode

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

Work on HIVE-26555 started by Teddy Choi.
-----------------------------------------
> Read-only mode
> --------------
>
>                 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: 20m
>  Remaining Estimate: 0h
>
> h1. Purpose
> In failover/fail-back scenarios, a Hive instance needs to be read-only, while other one is writable to keep a single source of truth.
> h1. Design
> EnforceReadOnlyHiveHook class can implement ExecuteWithHookContext interface. hive.exec.pre.hooks needs to have the class name to initiate an instance. "hive.enforce.readonly" can be configured to turn it on and off.
> h2. Allowed operations prefixes
>  * USE(or SWITCHDATABASE)
>  * SELECT
>  * DESC
>  * DESCRIBE
>  * SET
>  * EXPLAIN
>  * ROLLBACK
>  * KILL
>  * ABORT
> h1. Tests
>  * read_only_hook.q: USE, SHOW, DESC, DESCRIBE, EXPLAIN, SELECT
>  * read_only_hook_delete_failure.q
>  * read_only_hook_insert_failure.q
>  * read_only_hook_update_failure.q



--
This message was sent by Atlassian Jira
(v8.20.10#820010)