[WIP]HIVE-25542: Remove references to Index Configurations - #6815
Open
maheshrajus wants to merge 1 commit into
Open
maheshrajus wants to merge 1 commit into
maheshrajus wants to merge 1 commit into
Conversation
|
This branch has not been deployed
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
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?
Removes the obsolete hive.optimize.index.filter configuration and every reference to it.
Why are the changes needed?
Hive indexes were removed in 4.0.0 (HIVE-18715), but hive.optimize.index.filter survived as dead configuration. The
name is actively misleading — it no longer has anything to do with indexes; it gates ordinary predicate push-down
to the table scan, which hive.optimize.ppd already controls. Keeping it means two knobs for one behavior, a
confusing entry in the config docs, and hundreds of set lines in qtests that suggest a toggle users should care
about.
Does this PR introduce any user-facing change?
Yes, two:
no behavior change. Anyone explicitly setting it to false to suppress predicate push-down loses that control and
must use hive.optimize.ppd=false instead. With hive.conf.validation=true (the default), setting the removed key now
raises an unknown-config error rather than being silently ignored.
recommends only set hive.optimize.ppd=false.
How was this patch tested?
Existing tests