[HUDI-5545] Extending support to other special characters #7585
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
This fix is to cover issue as follows.
I am working on ingestion with S3 as source by following this blog . But 2nd job(S3EventsHoodieIncrSource) failing with
HoodieException: org.apache.hudi.exception.HoodieException: Path does not exist
. In our investigation, we have observed job failing due to encoded characters( these are being added by SQS) in S3 object name.When we deep dive in Hudi source code , we have observed Hudi decoding them in S3EventsMetaSelector & at the movement only = have handled.
FYI-
Original S3 object :
s3://<bucket>/s3_parquet_source_data/s3-test+0+0000061344.parquet
Encoded S3 object:
s3://<bucket>/s3_parquet_source_data/s3-test%2B0%2B0000061344.parquet
Note: workflow was running successfully if file name corrected.
Impact
See above.
Risk level
none
Documentation Update
N/A
Contributor's checklist