[HUDI-4449] Claim of RFC-98, Spark Datasource V2 Read #13609
Merged
+77
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Logs
First steps towards integrating of Spark Datasource V2 were taken in RFC-38, which is now marked as completed. However, there are multiple issues with advertising Hudi table as V2 without actual implementing certain API, and with using custom relation rule to fall back to V1 API. As a result, the current implementation of
HoodieCatalogandSpark3DefaultSourcereturns aV1Tableinstead ofHoodieInternalV2Table, in order to address performance regression.There was an attempt to implement Spark Datasource V2 read functionality as a regular task, but it failed due to the scope of work required. Therefore, this RFC proposes to discuss design of Spark Datasource V2 integration in advance and to continue working on it accordingly.
Impact
No impact at this stage
Risk level (write none, low medium or high below)
No
Documentation Update
No need at this stage
Contributor's checklist