Skip to content

feat(pyspark): expose merge_schema option in create_table #11071

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

Closed
wants to merge 1 commit into from

Conversation

NickCrews
Copy link
Contributor

Closes #10984

I didn't add any tests because I don't understand what this option does.
One of the requesters will need to explain this to me, and propose a general strategy for testing.

Another option would be to instead forward all kwargs opaquely as **backend_specific_kwargs, but I went with explicitly listing this as a named kwarg because that is what is already done with partition_by. But open to change this.

@github-actions github-actions bot added the pyspark The Apache PySpark backend label Apr 2, 2025
@cpcloud
Copy link
Member

cpcloud commented Jun 11, 2025

Closing this in favor of #11120 (which will be merged after the next release)

@cpcloud cpcloud closed this Jun 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pyspark The Apache PySpark backend
Projects
None yet
Development

Successfully merging this pull request may close these issues.

feat: add **options to pyspark backend create_table
4 participants