-
Notifications
You must be signed in to change notification settings - Fork 29.1k
[SPARK-28899][SQL][TEST] merge the testing in-memory v2 catalogs from catalyst and core #25610
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
Conversation
| if (tables.containsKey(ident)) { | ||
| throw new TableAlreadyExistsException(ident) | ||
| } | ||
|
|
||
| if (partitions.nonEmpty) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the sql/core version supports partitions, so the merged version should support partitions as well.
| import org.apache.spark.sql.util.CaseInsensitiveStringMap | ||
|
|
||
| // this is currently in the spark-sql module because the read and write API is not in catalyst | ||
| // TODO(rdblue): when the v2 source API is in catalyst, merge with TestTableCatalog/InMemoryTable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This TODO is completed in this PR.
|
Test build #109868 has finished for PR 25610 at commit
|
|
Test build #109869 has finished for PR 25610 at commit
|
|
Test build #109870 has finished for PR 25610 at commit
|
|
Test build #109894 has finished for PR 25610 at commit
|
|
+1 |
|
Merged to master. |
|
Yey! Congratulation, @rdblue !!! 😄 |
|
Thanks! |
|
@rdblue congrats and thanks for merging my PR! Hopefully this is your first Spark PR merging :) |
What changes were proposed in this pull request?
There are 2 in-memory
TableCatalogandTableimplementations for testing, in sql/catalyst and sql/core. This PR merges them.After merging, there are 3 classes:
InMemoryTableInMemoryTableCatalogStagingInMemoryTableCatalogFor better maintainability, these 3 classes are put in 3 different files.
Why are the changes needed?
reduce duplicated code
Does this PR introduce any user-facing change?
no
How was this patch tested?
N/A