yunqingmoswu opened a new pull request, #6655: URL: https://github.com/apache/inlong/pull/6655
### Prepare a Pull Request *(Change the title refer to the following example)* - Title: [INLONG-6654][Sort] Supports s3 side-output for dirty data *(The following *XYZ* should be replaced by the actual [GitHub Issue](https://github.com/apache/inlong/issues) number)* - Fixes #6654 ### Motivation Supports s3 side-output for dirty data, through it, dirty data can be archived to s3. This piece is designed as follows(some common process of dirty data side-output can view https://github.com/apache/inlong/pull/6618): 1. Add s3 side-output implements In this part, i will add dirty data cache and flush to s3 periodically. 2. Add s3 side-output factory to create object of s3 side-output ### Modifications 1.Add the core class S3DirtySink for dirty data side-output 2.Add S3DirtySinkFactory to create S3DirtySink 3.Add S3Options to config S3DirtySink 4.Add S3Helper to help side-output to s3 ### Verifying this change *(Please pick either of the following options)* - [ ] This change is a trivial rework/code cleanup without any test coverage. - [x] This change is already covered by existing tests, such as: *(please describe tests)* - [ ] This change added tests and can be verified as follows: *(example:)* - *Added integration tests for end-to-end deployment with large payloads (10MB)* - *Extended integration test for recovery after broker failure* ### Documentation - Does this pull request introduce a new feature? (yes / no) - If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented) - If a feature is not applicable for documentation, explain why? - If a feature is not documented yet in this PR, please create a follow-up issue for adding the documentation -- 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]
