maheshrajus opened a new pull request, #6815:
URL: https://github.com/apache/hive/pull/6815

   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/Hive/HowToContribute
     2. Ensure that you have created an issue on the Hive project JIRA: 
https://issues.apache.org/jira/projects/HIVE/summary
     3. Ensure you have added or run the appropriate tests for your PR: 
     4. If the PR is unfinished, add '[WIP]' in your PR title, e.g., 
'[WIP]HIVE-XXXXX:  Your PR title ...'.
     5. Be sure to keep the PR description updated to reflect all changes.
     6. Please write your PR title to summarize what this PR proposes.
     7. If possible, provide a concise example to reproduce the issue for a 
faster review.
   
   -->
   
   ### 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:                                                                    
                                      
                                                                                
                                        
     1. The config(hive.optimize.index.filter) is gone. Because 
hive.optimize.index.filter defaulted to true, anyone leaving it at the default 
sees 
     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.         
                                        
     2. Error message text changed in LeafFilterFactory for unsupported Parquet 
FilterPredicate conversions — it now    
     recommends only set hive.optimize.ppd=false.                               
                                        
    
   
   ### How was this patch tested?
   Existing tests


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to