codope opened a new pull request, #11975:
URL: https://github.com/apache/hudi/pull/11975

   ### Change Logs
   
   Suppose RLI (record index) is enabled on MOR table, do an insert and then 
delete a record. When table is not compacted, it is expected that RO 
(read-optimized) query shows the deleted record, while snapshot query will not. 
A query with no predicates works fine, but if the query has a predicate on 
record key field, it will use RLI and RLI always returns the latest snapshot. 
Hence, this PR fixes the issue by not using RLI for queries other than snapshot 
queries. The PR adds a new `supportsQueryType(queryType: HoodieTableQueryType)` 
API in the base class for index support. Different index can implement is 
differently as and when we add time tavel support for indexes.
    
   ### Impact
   
   Fix RO queries with RLI and record key predicate.
   
   ### Risk level (write none, low medium or high below)
   
   low
   
   ### Documentation Update
   
   _Describe any necessary documentation update if there is any new feature, 
config, or user-facing change. If not, put "none"._
   
   - _The config description must be updated if new configs are added or the 
default value of the configs are changed_
   - _Any new feature or user-facing change requires updating the Hudi website. 
Please create a Jira ticket, attach the
     ticket number here and follow the 
[instruction](https://hudi.apache.org/contribute/developer-setup#website) to 
make
     changes to the website._
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Change Logs and Impact were stated clearly
   - [ ] Adequate tests were added if applicable
   - [ ] CI passed
   


-- 
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]

Reply via email to