-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[fix](planner) fix current_timestamp param type mismatch when doing stream load #23092
Conversation
run buildall |
(From new machine)TeamCity pipeline, clickbench performance test result: |
run p0 |
PR approved by at least one committer and no changes requested. |
PR approved by anyone and no changes requested. |
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.
LGTM
run p0 |
7daf2af
4634c40
to
7daf2af
Compare
run buildall |
run buildall |
(From new machine)TeamCity pipeline, clickbench performance test result: |
PR approved by at least one committer and no changes requested. |
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.
LGTM
…tream load (#23092) FileLoadScanNode did not analyze the default value expr, result in target param type int32 become int8 as the original IntLiteral type.
…tream load (apache#23092) FileLoadScanNode did not analyze the default value expr, result in target param type int32 become int8 as the original IntLiteral type.
Proposed changes
Issue Number: close #23013
FileLoadScanNode did not analyze the default value expr, result in target param type int32 become int8 as the original IntLiteral type.
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...