HIVE-29520: Add configuration to enable/disable ACID functionality in Hive Metastore#6524
Open
VenuReddy2103 wants to merge 1 commit into
Open
HIVE-29520: Add configuration to enable/disable ACID functionality in Hive Metastore#6524VenuReddy2103 wants to merge 1 commit into
VenuReddy2103 wants to merge 1 commit into
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Introduce a configuration to enable/disable ACID functionality in Hive Metastore
Why are the changes needed?
With the increasing adoption of the Apache Iceberg table format, many deployments no longer rely on ACID (transactional) tables provided by Apache Hive. In such environments, ACID-related functionality in the Hive Metastore becomes unnecessary.
Currently, Hive Metastore initializes and runs several background threads and services that are specifically designed to support ACID operations (e.g., compaction handling, transaction management, cleanup tasks). These components continue to run regardless of whether ACID tables are actually used in the deployment.
Running ACID-related services in environments that do not use ACID tables leads to:
Unnecessary resource consumption (CPU, memory, threads)
Increased operational overhead
Additional complexity in debugging and monitoring
Longer startup times and maintenance burden
Providing a mechanism to disable ACID functionality would streamline such deployments and improve efficiency.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Added unittests