Open scchengaiah opened 1 year ago
SODA-1786
SODA-1786 @jmarien Could you please share the respective link or elaborate ? Is there an issue already opened for this.
Hi @scchengaiah, thank you for reaching out!
The previous message was an automatic message triggered by the integration with our ticketing system.
I will reach out to the engineering team to see if there is a current workaround to achieve what you are describing.
Out of curiosity, could you let me know why you want to extract the generated SQL?
Thanks a lot!
@benjamin-pirotte : Thank you for the response.
We want to use SQL parsers to detect the tables and the columns involved from the generated SQL query and link to the failed checks.
We believe that this can help our data analysts to quickly get the relevant information on a particular check in case of complex SQL statements. Also, the generated SQL shall be executed manually which can help to decide the next set of actions.
@benjamin-pirotte : Do we have any update from the engineering team ?
Dear All,
I want to extract the SQL queries generated for every check defined in the checks.yml file via Python API.
I could able to visualize the SQL queries when I set the Verbose flag to True in the scan results JSON. However, I could not connect these generated SQL's with the checks. I could not find any id or reference information that indicates the SQL is for a particular check.
Could you please suggest if there is an approach to handle this ?
Please find below the initial analysis. Expectation is to iterate through the checks array and fetch all the failed checks. For each of the failed check, extract the SQL generated.
Unable to identify a common relation between the check object attributes and the log generated. Any standard pattern to fetch this information can be helpful as well 🙂.
checks.yml:
JSON Logs: