[SPARK-52326][SQL] Add partitions related ExternalCatalogEvent and post them in corresponding operations #51030
+203
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
waterlx
changed the title
waterlx
changed the title
|
@gatorsmile @dongjoon-hyun Can you help to review this PR? Thanks! |
waterlx
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Add Partitions related events, for the following external catalog operations: create / drop / alter / rename. A base "PartitionsEvent" is added by extending "TableEvent". One "PartitionsEvent" (and its subs) could contain the operation for one or more partitions. So it is named as "Partition
sEvent" in plural form, so are its subs.Post those events in the corresponding external catalog operations
Why are the changes needed?
The operation list extracted from Spark events are of great help for user to summarize what have been done against a db/table/function/partition, for the purpose of logging and/or auditing.
In ExternalCatalogWithListener, there are events posted against db, table and function for all registered listeners. But an operation against operation does not have its event posted.
Does this PR introduce any user-facing change?
With this change, partition related operations are posted into register listener as events
How was this patch tested?
Enrich UT and also tested on local cluster
Was this patch authored or co-authored using generative AI tooling?
No