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

   ### Change Logs
   
   This PR fixes 2 issues in schema evolution client api:
   
   1. Lost operation field in avro schema
   2. Not found schema for table
   ```
   org.apache.hudi.exception.HoodieException: cannot find schema for current 
table: /tmp/hudi
        at 
org.apache.hudi.client.BaseHoodieWriteClient.getInternalSchemaAndMetaClient(BaseHoodieWriteClient.java:1767)
        at 
org.apache.hudi.client.BaseHoodieWriteClient.addColumn(BaseHoodieWriteClient.java:1673)
        at 
org.apache.hudi.sink.TestWriteCopyOnWrite.test(TestWriteCopyOnWrite.java:454)
   ```
   Introduced new test `TestSchemaEvolutionClient`for schema evolution client 
api.
   
   Flink schema evolution https://github.com/apache/hudi/pull/5830 requires 
these fixes
   
   ### Impact
   
   Fixed lost operation field in avro schema and not found schema for table
   
   ### Risk level
   
   Low. 
   
   ### Documentation Update
   
   _Describe any necessary documentation update if there is any new feature, 
config, or user-facing change_
   
   - _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