Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Migrate Tables Error Handling - Request for offending table or view name in logs #4438

@gs-dbx

Description

@gs-dbx

Is there an existing issue for this?

  • I have searched the existing issues

Problem statement

When a user runs migrate-tables against an environment, we are seeing an exception with sqlglot (version 26.8.0) in the view_migrate.py file, line 29 where UCX reports an error with the DDL for the view (based on sqlglot), however, the logs don't report the name of the offending view making it very difficult to troubleshoot.

In addition, separately applying sqlglot in a script against the same views does not yield a similar error or exception, so it may be possible that this is representative of a different or larger problem.

Proposed Solution

At a minimum add logging to reflect views causing an exception in view_migrate.py and table_migrate.py.

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions