Skip to content

[SPARK-41049][SQL][FOLLOW-UP][3.5] stateful expressions test uses different pretty name#46795

Closed
amaliujia wants to merge 2 commits intoapache:branch-3.5from
amaliujia:branch-3.5
Closed

[SPARK-41049][SQL][FOLLOW-UP][3.5] stateful expressions test uses different pretty name#46795
amaliujia wants to merge 2 commits intoapache:branch-3.5from
amaliujia:branch-3.5

Conversation

@amaliujia
Copy link
Contributor

What changes were proposed in this pull request?

We need use a different pretty string for the stateful expression test case in branch-3.5.

Why are the changes needed?

Fix the failing test case.

Does this PR introduce any user-facing change?

NO

How was this patch tested?

Existing UT

Was this patch authored or co-authored using generative AI tooling?

NO

@github-actions github-actions bot added the SQL label May 29, 2024
@amaliujia
Copy link
Contributor Author

@cloud-fan

@cloud-fan
Copy link
Contributor

the test failure is unrelated, merging to 3.5!

@HyukjinKwon HyukjinKwon changed the title [3.5][SPARK-41049][SQL][FOLLOW-UP] stateful expressions test uses different pretty name [SPARK-41049][SQL][FOLLOW-UP][3.5] stateful expressions test uses different pretty name May 30, 2024
cloud-fan pushed a commit that referenced this pull request May 30, 2024
…ferent pretty name

### What changes were proposed in this pull request?

We need use a different pretty string for the stateful expression test case in branch-3.5.

### Why are the changes needed?

Fix the failing test case.

### Does this PR introduce _any_ user-facing change?

NO

### How was this patch tested?

Existing UT

### Was this patch authored or co-authored using generative AI tooling?

NO

Closes #46795 from amaliujia/branch-3.5.

Authored-by: Rui Wang <rui.wang@databricks.com>
Signed-off-by: Wenchen Fan <wenchen@databricks.com>
@cloud-fan cloud-fan closed this May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants