-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](hive) Incorrect location conversion #46362
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-H: Total hot run time: 32562 ms |
TPC-DS: Total hot run time: 191245 ms |
ClickBench: Total hot run time: 31.35 s |
| locationParams.setWritePath(storageLocation); | ||
| locationParams.setOriginalWritePath(location); | ||
| locationParams.setTargetPath(location); | ||
| locationParams.setOriginalWritePath(sd.getLocation()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
duplicate call of setOriginalWritePath
|
run buildall |
TPC-H: Total hot run time: 34032 ms |
TPC-DS: Total hot run time: 197517 ms |
ClickBench: Total hot run time: 31.42 s |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
### What problem does this PR solve? Problem Summary: For the "original_write_path" field, when the location is of the S3 type, it should not be converted into the S3 schema. Instead, the original location should be retained.
### What problem does this PR solve? Problem Summary: For the "original_write_path" field, when the location is of the S3 type, it should not be converted into the S3 schema. Instead, the original location should be retained.
### What problem does this PR solve? Problem Summary: For the "original_write_path" field, when the location is of the S3 type, it should not be converted into the S3 schema. Instead, the original location should be retained.
### What problem does this PR solve? Related PR: #46362 Problem Summary: For the "target_path" field, when the location is of the S3 type, it should not be converted into the S3 schema.
### What problem does this PR solve? Related PR: #46362 Problem Summary: For the "target_path" field, when the location is of the S3 type, it should not be converted into the S3 schema.
Related PR: apache#46362 Problem Summary: For the "target_path" field, when the location is of the S3 type, it should not be converted into the S3 schema.
### What problem does this PR solve? Related PR: apache#46362 Problem Summary: For the "target_path" field, when the location is of the S3 type, it should not be converted into the S3 schema.
### What problem does this PR solve? Related PR: apache#46362 Problem Summary: For the "target_path" field, when the location is of the S3 type, it should not be converted into the S3 schema.
What problem does this PR solve?
Problem Summary:
For the "original_write_path" field, when the location is of the S3 type, it should not be converted into the S3 schema. Instead, the original location should be retained.
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)