vaibhavk1992 opened a new pull request, #903: URL: https://github.com/apache/incubator-xtable/pull/903
- testVariousOperationsDeltaKernelSource runs the same dataset-equivalence checks as testVariousOperations, forcing DeltaKernelConversionSourceProvider across both sync modes and both partitioning cases. - testVariousOperationsDeltaKernelTarget does the same for the DELTA target leg, routing through DeltaKernelConversionTarget via DeltaConversionTargetConfig.USE_KERNEL, using ConversionTargetFactory's normal dispatch path. - testVariousOperations body extracted into runVariousOperationsTest so both new tests share the same assertions the Standalone paths are validated with; existing Standalone matrix is unchanged. The target-side test currently fails: DeltaKernelConversionTarget only calls withSchema() on table creation, so schema evolution on an existing table (e.g. a new nested field added inside an array column) never reaches the Delta log's Metadata action. Traced to open upstream gap delta-io/delta#4305. Follow-up fail-fast guard tracked separately. ## *Important Read* - *Please ensure the GitHub issue is mentioned at the beginning of the PR* ## What is the purpose of the pull request *(For example: This pull request implements the sync for delta format.)* ## Brief change log *(for example:)* - *Fixed JSON parsing error when persisting state* - *Added unit tests for schema evolution* ## Verify this pull request *(Please pick either of the following options)* This pull request is a trivial rework / code cleanup without any test coverage. *(or)* This pull request is already covered by existing tests, such as *(please describe tests)*. (or) This change added tests and can be verified as follows: *(example:)* - *Added integration tests for end-to-end.* - *Added TestConversionController to verify the change.* - *Manually verified the change by running a job locally.* -- 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]
