[FIX](regresstest) fix cases for test_nested_types_insert_into_with_s3#25228
Merged
Conversation
Contributor
Author
|
run buildall |
Contributor
Author
|
run p0 |
Contributor
|
run p0 |
Contributor
|
PR approved by anyone and no changes requested. |
Contributor
Author
|
run p0 |
1 similar comment
Contributor
Author
|
run p0 |
github-actions
Bot
added
the
approved
Contributor
|
PR approved by at least one committer and no changes requested. |
xiaokang
pushed a commit
that referenced
this pull request
Oct 13, 2023
dutyu
pushed a commit
to dutyu/doris
that referenced
this pull request
Oct 28, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Proposed changes
Issue Number: close #xxx
here need truncate table for insert into same table with parquet file which data is not same with orc file,
so next select from parquet may has 50% chance to fail
we can truncate table first.
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...