You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When the hereditary extraction pipeline is executed, it is only partially successful. However, the execution process does not indicate which table failed.
I executed the pipeline for 8 hours and it was partially successful. However, the problem was caused by a lack of permissions on one of the tables. The current log only shows the following information, which is not enough to help me find the table name of the error from thousands of tables
| Source | Unhandled | Encountered exception running step [<metadata.ingestion.source.database.unitycatalog.lineage.UnitycatalogLineageSource object at 0x7395cf06f1f0>]: [Table Name should be informed, but got table=`None`] | Traceback (most recent call last):
Describe the solution you'd like
Add debug log in UnityCatalog Client to print the name of the table being processed
Describe alternatives you've considered
Enhance the error message, add query conditions provided by pre-step when query fails
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When the hereditary extraction pipeline is executed, it is only partially successful. However, the execution process does not indicate which table failed.
I executed the pipeline for 8 hours and it was partially successful. However, the problem was caused by a lack of permissions on one of the tables. The current log only shows the following information, which is not enough to help me find the table name of the error from thousands of tables
Describe the solution you'd like
Add debug log in UnityCatalog Client to print the name of the table being processed
Describe alternatives you've considered
Enhance the error message, add query conditions provided by pre-step when query fails
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: