HIVE-26555 Read-only mode

[pudidic]

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

[sonarqubecloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
7 Code Smells

No Coverage information
No Duplication information

[github-actions[bot]]

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.

[abstractdog]

thanks for clarifying @pudidic , implementation looks good to me +1, pending tests

[sonarqubecloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
7 Code Smells

No Coverage information
No Duplication information

[pudidic]

Thank you @abstractdog !