Skip to content

engine: Incorrect status message fix - #1917

Merged
DanCodedThis merged 2 commits into
mainfrom
DanCodedThis/1916-incorrect-status-message-fix
Nov 8, 2025
Merged

engine: Incorrect status message fix#1917
DanCodedThis merged 2 commits into
mainfrom
DanCodedThis/1916-incorrect-status-message-fix

Conversation

@DanCodedThis

@DanCodedThis DanCodedThis commented Nov 8, 2025

Copy link
Copy Markdown
Contributor

Closes #1916

  • Before for arrow we sent an empty null array. Which resulted in a seg-fault of the snowflake cli
  • For json we sent No data - an empty array.
  • Both were incorrect, changed to one status column with a successful execution message
  • Added insta tests
  • Checked other statements which use the status response and fixed their snapshots also

P.S. Alter & Use don't check if the variable exists (only the type I assume), so it always says it is successful, it did that before, but just didn't send the message. Drop should check. Set is probably infallible, either, then sql "comp" errors.

@github-actions

github-actions Bot commented Nov 8, 2025

Copy link
Copy Markdown
Contributor

SLT Targeted Testing: No relevant SLT tests found for the changes in this PR. No testing required.

@DanCodedThis
DanCodedThis merged commit 9bc3cbc into main Nov 8, 2025
7 checks passed
@DanCodedThis
DanCodedThis deleted the DanCodedThis/1916-incorrect-status-message-fix branch November 8, 2025 16:47
Ok(QueryResult::new(
vec![RecordBatch::new_empty(schema.clone())],
vec![
RecordBatch::try_new(

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually think that this should not be fixed query executor modifying QueryResult. This "Statement executed ..." message that was added looks like belongs to a rest api. It naturally belongs to the snowflake-rest.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also I believe that such change should be covered by a separate test in snowlake-rest as well

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably do that later, I agree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

engine: Incorrect status response with arrow format

3 participants