[MINOR][DNM][TESTING] Flink bundle testing 5.5 #11326
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…pache#9634) Unify the encoding of Java `String` to byte array in Hudi, especially for writing bytes to the storage, by using `UTF_8` encoding only. --------- Co-authored-by: Sagar Sumit <[email protected]>
…emove dependency (apache#9649)
Co-authored-by: Jonathan Vexler <=> Co-authored-by: Y Ethan Guo <[email protected]>
…nt-common to hudi-common (apache#9103) Co-authored-by: Y Ethan Guo <[email protected]>
This commit fixes the bundling of RoaringBitmap dependency in Hudi bundles by including it in the shade rules and shading the classes, to avoid dependency conflict with engine-provided jars, e.g., Spark. Before this fix, with Hudi Spark bundle, NoSuchMethodError exception is thrown by Spark 3.2.
* Address build failures in older Flink Versions * Remove unnecessary dependency on flink-connector-hive * Fix Flink 1.18 Validate-bundles --------- Signed-off-by: Prabhu Joseph <[email protected]> Co-authored-by: Prabhu Joseph <[email protected]> Co-authored-by: root <[email protected]>
--------- Co-authored-by: Shawn Chang <[email protected]> Co-authored-by: Y Ethan Guo <[email protected]>
… prevent inconsistency during data reads (apache#10711)
…rmats (apache#10265) * [HUDI-7190] Fix legacy parquet format nested columns vectorized read for spark3.3+ * Fix nested type implicit schema evolution * fix legacy format support batch read * Add exception messages when vectorized read nested type with type change
…ool (apache#10374) Co-authored-by: jp0317 <[email protected]>
…ansitionPendingState (apache#10392)
…pache#10411) Co-authored-by: xuyu <[email protected]>
… with append mode (apache#10430) Co-authored-by: xuyu <[email protected]>
…to specify hoodie.properties path (apache#10413)
Co-authored-by: dongsj <[email protected]>
This aligns with the doc change here: apache#10680
…ache#10689) * fix npe * add empty table support as well * use empty relation * fix failing tests --------- Co-authored-by: Jonathan Vexler <=>
We have support for filtering the input files based on an extension (custom) for GCS Incr Source that can be configured. But we don't have the same for the S3 incr source (which always assumes that file extension is same as the format which may not be the case always). Co-authored-by: rmahindra123 <[email protected]>
…e in sparksql (apache#10703) * [HUDI-7423] Support table type name case-sensitive when create table in sparksql * add comments
…er methods for S3/GCS sources (apache#10701)
…ap with '.hadoop' (apache#10686) Co-authored-by: Vova Kolmakov <[email protected]>
Co-authored-by: Vova Kolmakov <[email protected]>
…ests to prevent infinite loops (apache#10738)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Describe context and summary for this change. Highlight if any code was copied.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".
ticket number here and follow the instruction to make
changes to the website.
Contributor's checklist