Closed phalcon22 closed 7 months ago
The issue comes from when we handling session metadata. The intention for session metadata is that for temporary table/view created during the session, the schema info won't be available in metadata, as the table/view is not created yet.
But clearly we should limit the scope of session metadata to CREATE (and maybe INSERT). By now means should we register session metadata for UPDATE statement.
In this case, we register session metadata for dataset.table_1
through UPDATE, which doesn't include any schema information. And in the end this masks the schema info from MetaDataProvider.
Describe the bug
SQL
To Reproduce Note here we refer to SQL provided in prior step as stored in a file named
test.sql
Metadata.json:
Result
Expected behavior
Python version (available via
python --version
)SQLLineage version (available via
sqllineage --version
):Notes