Repository navigation
[Fix](hive-writer) Fix s3 file commiter not working. - #35502
Conversation
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
fa48db1 to
d43df71
Compare
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 41380 ms |
TPC-DS: Total hot run time: 172652 ms |
|
TeamCity be ut coverage result: |
ClickBench: Total hot run time: 30.37 s |
### Issue `The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed. (Service: S3, Status Code: 404, Request ID: 66557027E897233333FFC198)` ### Root cause apache#35311 adjusted the order of building hive partition update information. This change caused the update id to be unable to be obtained, causing the s3 file committer to not work properly. ### Solution Because uploading to s3 occurs after s3 file writer close(), close() must be called first, and then the build hive partiton update information is called.
bp #35502 Co-authored-by: Qi Chen <[email protected]>
### Issue `The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed. (Service: S3, Status Code: 404, Request ID: 66557027E897233333FFC198)` ### Root cause #35311 adjusted the order of building hive partition update information. This change caused the update id to be unable to be obtained, causing the s3 file committer to not work properly. ### Solution Because uploading to s3 occurs after s3 file writer close(), close() must be called first, and then the build hive partiton update information is called.
### Issue `The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed. (Service: S3, Status Code: 404, Request ID: 66557027E897233333FFC198)` ### Root cause apache#35311 adjusted the order of building hive partition update information. This change caused the update id to be unable to be obtained, causing the s3 file committer to not work properly. ### Solution Because uploading to s3 occurs after s3 file writer close(), close() must be called first, and then the build hive partiton update information is called.
Proposed changes
Issue
The specified upload does not exist. The upload ID may be invalid, or the upload may have been aborted or completed. (Service: S3, Status Code: 404, Request ID: 66557027E897233333FFC198)Root cause
#35311 adjusted the order of building hive partition update information. This change caused the update id to be unable to be obtained, causing the s3 file committer to not work properly.
Solution
Because uploading to s3 occurs after s3 file writer close(), close() must be called first, and then the build hive partiton update information is called.
Further comments
If this is a relatively large or complex change, kick off the discussion at [email protected] by explaining why you chose the solution you did and what alternatives you considered, etc...