Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
4.0.0
Description
The `ParserUtils.unescapeSQLString` method is currently implemented using regexes for part of the parsing, but is costly because multiple Matcher instances are created for every input cahracter.
I think that we should optimize this to remove the use of regexes.
I will submit a PR for this.
Attachments
Issue Links
- relates to
-
SPARK-34263 Simplify the code for treating unicode/octal/escaped characters in string literals
- Resolved
- links to