Sweep: Execute dbt SQL fails if the query starts with a Jinga comment #1158
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request addresses an issue where executing dbt SQL statements that begin with a Jinja comment causes failures. It introduces a fix by stripping leading Jinja comments from the SQL statement before execution.
Summary
re
module indbt_core_integration.py
to utilize regular expressions for processing SQL statements.execute_sql
method to remove Jinja comments from the start of the SQL statement. This ensures that SQL queries starting with Jinja comments are executed without errors.execute_sql
function of thedbt_core_integration.py
file, enhancing its robustness in handling SQL queries with Jinja syntax.Fixes #1156.
💡 To get Sweep to edit this pull request, you can:
This is an automated message generated by Sweep AI.