rishav23 opened a new pull request, #56062:
URL: https://github.com/apache/spark/pull/56062
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'common/utils/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
This PR makes Spark Connect Catalog.createTable eager. Previously,
createTable() only constructed a lazy DataFrame, requiring users to explicitly
trigger an action such as .collect() for the table creation to actually
execute. This change eagerly executes the command internally while preserving
the existing return type. A regression test has also been added to verify that
tables are created immediately without requiring an explicit action.
### Why are the changes needed?
Catalog.createTable() is a side-effecting operation and should execute
eagerly to match expected Catalog API semantics.
### Does this PR introduce _any_ user-facing change?
Yes. Previously spark.catalog.createTable(....) did not immediately create
the table in Spark Connect unless an action was triggered. Now the table is
created eagerly.
### How was this patch tested?
- Added a regression test in CatalogSuite
- Ran build/sbt compile
### Was this patch authored or co-authored using generative AI tooling?
No
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
