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

   ### Change Logs
   
   This PR fixes two issues:
   
   1. When a functional index is updated, it was getting re-initialized. This 
was happening because metadata partition type only contains the functional 
index partition prefix while hoodie.properties contains the full name. Due to 
discrepancy, metadata writer thought there is anew index that needs ot be 
initialized. This is fixed in `HoodieTableConfig#isMetadataPartitionAvailable`.
   2. When a functional index is updated, it fetches latest file slices, 
including the pending ones, in data partition. There was a typo in building the 
filesystem view. Instead of passing data meta client, metadata meta client was 
passed.
   
   Added a test which covers both these scenarios.
   
   ### Impact
   
   Fixes functional index bugs.
   
   ### 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