Skip to content

Conversation

@harshmotw-db
Copy link
Contributor

@harshmotw-db harshmotw-db commented Nov 26, 2025

What changes were proposed in this pull request?

This PR enables shredding and variant logical type annotation configs by default. However, some test suites assume the old behavior. This PR fixes those tests to also work with the new default configs.

This PR also fixes a bug we discovered in the previous PR where variant default resolution would fail when pushVariantIntoScan was enabled.

Why are the changes needed?

To fix the bug.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Existing tests.

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

No.

@cloud-fan
Copy link
Contributor

@harshmotw-db let's create a new JIRA ticket for this.

@harshmotw-db harshmotw-db changed the title [SPARK-54454][PART-1] Fix default resolution during variant pushdown and prepare test suites for default enablement of shredding and variant logical type annotation [SPARK-54522][SPARK-54523] Fix default resolution during variant pushdown and prepare test suites for default enablement of shredding and variant logical type annotation Nov 26, 2025
@harshmotw-db
Copy link
Contributor Author

@cloud-fan I have created two new Jiras

@cloud-fan cloud-fan changed the title [SPARK-54522][SPARK-54523] Fix default resolution during variant pushdown and prepare test suites for default enablement of shredding and variant logical type annotation [SPARK-54523] Fix default resolution during variant pushdown and prepare test suites for default enablement of shredding and variant logical type annotation Nov 26, 2025
@dongjoon-hyun dongjoon-hyun changed the title [SPARK-54523] Fix default resolution during variant pushdown and prepare test suites for default enablement of shredding and variant logical type annotation [SPARK-54523][SQL] Fix default resolution during variant pushdown Nov 26, 2025
Copy link
Member

@dongjoon-hyun dongjoon-hyun left a comment

Choose a reason for hiding this comment

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

+1, LGTM (if CI passes). Thank you.

To be clear, I removed the following clauses from the PR title and description because we didn't make a decision for the flag, @harshmotw-db and @cloud-fan .

  • prepare test suites for default enablement of shredding and variant logical type annotation
  • For default enablement of variant logical type annotation and shredding.

@cloud-fan
Copy link
Contributor

thanks, merging to master/4.1!

@cloud-fan cloud-fan closed this in d36bd62 Nov 26, 2025
cloud-fan added a commit that referenced this pull request Nov 26, 2025
### What changes were proposed in this pull request?

[This PR](#53164) enables shredding and variant logical type annotation configs by default. However, some test suites assume the old behavior. This PR fixes those tests to also work with the new default configs.

This PR also fixes a bug we discovered in the previous PR where variant default resolution would fail when pushVariantIntoScan was enabled.

### Why are the changes needed?

To fix the bug.

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

No.

### How was this patch tested?

Existing tests.

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

No.

Closes #53224 from harshmotw-db/harshmotw-db/shredding_fixes.

Lead-authored-by: Harsh Motwani <harsh.motwani@databricks.com>
Co-authored-by: Wenchen Fan <cloud0fan@gmail.com>
Signed-off-by: Wenchen Fan <wenchen@databricks.com>
(cherry picked from commit d36bd62)
Signed-off-by: Wenchen Fan <wenchen@databricks.com>
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.

3 participants