Skip to content

branch-4.0: [fix](Hive) Fix insert failure for non-partitioned object storage tables #58624

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.

Sign up for GitHub

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

Jump to bottom
Merged
morningman merged 1 commit into from
Dec 2, 2025
Merged

branch-4.0: [fix](Hive) Fix insert failure for non-partitioned object storage tables #58624

morningman merged 1 commit into from
Dec 2, 2025

Conversation

@CalvinKirs
Copy link
Member

@CalvinKirs CalvinKirs commented Dec 2, 2025

@CalvinKirs
[fix](Hive) Fix insert failure for non-partitioned object storage tables
3364af4 
### Problem

````
copy file failed: software.amazon.awssdk.services.s3.model.NoSuchKeyException: The specified key does not exist. (Service: S3, Status Code: 404,

```
Inserting into non-partitioned object storage tables fails because the BE (Backend) treats non-partitioned and partitioned tables differently. Partitioned tables always append a folder suffix for each partition, and all data is organized by partition folders. Non-partitioned tables do not require partition information, but it was being set, causing insert failures.

### Solution
- Skip setting partition information for non-partitioned tables in the BE.
- Maintain current behavior for partitioned tables, including folder suffix handling.

### Result
- Inserts into non-partitioned object storage tables succeed.
- Partitioned tables continue to work as expected.
@CalvinKirs CalvinKirs requested a review from yiguolei as a code owner December 2, 2025 07:52
@CalvinKirs
Copy link
Member Author

CalvinKirs commented Dec 2, 2025

run buildall

@Thearas
Copy link
Contributor

Thearas commented Dec 2, 2025

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@github-actions github-actions bot added the approved Indicates a PR has been approved by one committer. label Dec 2, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2025

PR approved by at least one committer and no changes requested.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2025

PR approved by anyone and no changes requested.

@morningman morningman merged commit f3067b3 into apache:branch-4.0 Dec 2, 2025
25 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@yiguolei yiguolei yiguolei approved these changes

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by one committer. reviewed

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@CalvinKirs @Thearas @yiguolei @morningman