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

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HIVE-26555?focusedWorklogId=811189&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-811189 ]

ASF GitHub Bot logged work on HIVE-26555:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Sep/22 12:16
            Start Date: 22/Sep/22 12:16
    Worklog Time Spent: 10m 
      Work Description: pudidic opened a new pull request, #3614:
URL: https://github.com/apache/hive/pull/3614

   ### What changes were proposed in this pull request?
   Introduces a read-only mode.
   
   ### Why are the changes needed?
   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.
   
   ### Does this PR introduce _any_ user-facing change?
   Yes. 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.
   
   Allowed operations prefixes
   * USE(or SWITCHDATABASE)
   * SELECT
   * DESC
   * DESCRIBE
   * SET
   * EXPLAIN
   * ROLLBACK
   * KILL
   * ABORT
   
   ### How was this patch tested?
   * 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
   




Issue Time Tracking
-------------------

            Worklog Id:     (was: 811189)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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
>          Time Spent: 10m
>  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)