This message was deleted.
# secoda-supportw
wooden-spring-14915
05/17/2023, 12:37 AMThis message was deleted.
w
white-honey-61500
05/17/2023, 1:51 PMHi @little-portugal-52201 let me look into this for you!'
white-honey-61500
05/17/2023, 3:45 PMcc: @lively-helicopter-98030 🙂
🙌 1
l
lively-helicopter-98030
05/19/2023, 3:22 PMHi @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 🙂
lively-helicopter-98030
05/19/2023, 3:39 PMThe approach I am thinking is to add a field to
meta.batch_spec.data_asset_namemeta.batch_spec.data_asset_namesdatabase_name.schema_name.table_namew
white-honey-61500
05/24/2023, 3:09 PMHi @little-portugal-52201 this should be resolved now! Please let us know if you're still seeing any issues
6 Views