[
https://issues.apache.org/jira/browse/SPARK-22405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226724#comment-16226724
]
Saisai Shao commented on SPARK-22405:
-------------------------------------
Thanks [~cloud_fan] for your comments. Using fake {{ExternalCatalog}} to
delegate might be one solution, but this will also force user to use this
custom {{ExternalCatalog}} only as far as I know. This might be OK for the end
user, but for us who will deliver packages to user, such restriction seems not
so feasible.
> Enrich the event information and add new event of ExternalCatalogEvent
> ----------------------------------------------------------------------
>
> Key: SPARK-22405
> URL: https://issues.apache.org/jira/browse/SPARK-22405
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 2.2.0
> Reporter: Saisai Shao
> Priority: Minor
>
> We're building a data lineage tool in which we need to monitor the metadata
> changes in {{ExternalCatalog}}, current {{ExternalCatalog}} already provides
> several useful events like "CreateDatabaseEvent" for custom SparkListener to
> use. But the information provided by such event is not rich enough, for
> example {{CreateTablePreEvent}} only provides "database" name and "table"
> name, not all the table metadata, which is hard for user to get all the table
> related useful information.
> So here propose to and new {{ExternalCatalogEvent}} and enrich the current
> existing events for all the catalog related updates.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
