fix: address escape literal issue #21516#21599
Draft
SamAya21 wants to merge 2 commits intoapache:mainfrom
Draft
Conversation
Contributor
|
Few points before the actual code review:
|
Author
|
Sorry about that, I hadn't seen I should've ran sqllogictests. How exactly would I run the linter locally or what webpage would I find that as I see that I had forgot to add the header to a test file I had created. |
Contributor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which issue does this PR close?
Closes #21516
Rationale for this change
Issue #21516 reports that Spark-mode SQL string literals such as '\thello' and '\nhello' are treated as literal backslash text instead of using Spark-compatible escape handling. This fix should address all string functions not just soundex and length. This should improve matching functionality between pyspark and datafusion-spark
What changes are included in this PR?
Are these changes tested?
Yes. I tested the change with these commands:
cargo test -p datafusion
cargo test -p datafusion-sql
cargo test -p datafusion-spark
cargo test --profile=ci --test sqllogictests
Are there any user-facing changes?
Yes, there are user-facing changes. In Spark mode, SQL string literals now use Spark-compatible backslash escape handling. Generic DataFusion SQL behavior is unchanged.