[
https://issues.apache.org/jira/browse/IMPALA-15093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18091365#comment-18091365
]
ASF subversion and git services commented on IMPALA-15093:
----------------------------------------------------------
Commit 9957737efe3f5a6d3ecec816627d287e37d0a950 in impala's branch
refs/heads/master from Gokul Kolady
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=9957737ef ]
IMPALA-15093: Use RE2 For Profile Analyzer Regex
Replace std::regex usage in query profile parsing/redaction with
re2::RE2 so the AI analyzer flow uses a single regex engine
end-to-end. This updates pattern definitions and
matching/replacement/extraction paths (query ID,
fragment/operator parsing, resource estimate parsing, and
redaction token collection) while preserving existing behavior.
Testing:
I re-ran query-profile-redaction-test and
query-profile-parsing-tools-test, including the new unit tests
added in this change to cover RE2-based redaction token
collection and mixed-unit duration parsing/ratio logic.
Change-Id: Ie1343b2f049758e862d229f2a647273de56855c4
Reviewed-on: http://gerrit.cloudera.org:8080/24446
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Use RE2 For Profile Analyzer Regex
> ----------------------------------
>
> Key: IMPALA-15093
> URL: https://issues.apache.org/jira/browse/IMPALA-15093
> Project: IMPALA
> Issue Type: Improvement
> Reporter: Gokul Kolady
> Assignee: Gokul Kolady
> Priority: Major
>
> We should migrate to RE2 for all regex-related processing in the Impala AI
> Query Profile Analyzer flow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
