Fix BigQuery string literal apostrophe escaping issue in filters (#35857)#40455
Fix BigQuery string literal apostrophe escaping issue in filters (#35857)#40455Jualhosting wants to merge 3 commits into
Conversation
Code Review Agent Run #c823cbActionable Suggestions - 0Additional Suggestions - 2
Review Details
Bito Usage GuideCommands Type the following command in the pull request comment and save the comment.
Refer to the documentation for additional commands. Configuration This repository uses Documentation & Help |
|
The PR comments file contains only one comment entry, which matches the suggestion in question. The suggestion is valid and addresses a logic error in the BigQuery literal compiler. The current implementation escapes single quotes but leaves backslashes untouched, which can lead to invalid SQL when values end with a backslash. The suggested fix is to escape backslashes before apostrophes or use the dialect literal processor to ensure valid string literals for all inputs. superset/db_engine_specs/bigquery.py superset/db_engine_specs/bigquery.py |
|
/resolve |
…satisfy unit tests
Code Review Agent Run #5b7de6Actionable Suggestions - 0Review Details
Bito Usage GuideCommands Type the following command in the pull request comment and save the comment.
Refer to the documentation for additional commands. Configuration This repository uses Documentation & Help |
Fixes #35857 by overriding BindParameter compilation for bigquery dialect to use backslash escaping for single quotes.
SUMMARY
Fixes BigQuery string literal apostrophe escaping issue in filters by overriding the
BindParametercompilation for the BigQuery dialect to use backslash escaping.BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
Unit tests verify the correct escaping behavior for the BigQuery dialect.
ADDITIONAL INFORMATION
AI Assistance Disclosure
This PR was developed with the assistance of Antigravity (a Gemini-based AI coding assistant). The contributor has reviewed and validated all changes.