This message was deleted.
# secoda-support
w
This message was deleted.
w
Hi @little-portugal-52201 let me look into this for you!'
cc: @lively-helicopter-98030 🙂
🙌 1
l
Hi @little-portugal-52201, it seems most if not all of the validations from the PROD integration are using Custom SQL Queries to pull the tables. Which is why Secoda is unable to pull any sort of lineage metadata because there are no references to which tables are being queried. Do you have scripts and/or Jupyter notebooks you are using to create these expectations? We can take another approach, where you are injecting which tables are being queried in each of the validations (will have to do a bit of investigating from my end, but will keep you posted here). If you are able to share how you created the expectation or the file itself (with the sensitive data obfuscated ofcourse), that would be incredibly helpful 🙂
The approach I am thinking is to add a field to
meta.batch_spec.data_asset_name
or
meta.batch_spec.data_asset_names
(for multiple) and you can populate it with the
database_name.schema_name.table_name
and then we can easily parse that 🙂
w
Hi @little-portugal-52201 this should be resolved now! Please let us know if you're still seeing any issues