Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Refactor] Chop too large hyperscan regex pattern when logging it on an error #52467

Merged

Conversation

satanson
Copy link
Contributor

Why I'm doing:

When hypercan patten exceeds some threshold(30KB+), hyperscan compilation report error and log the error, the size of be log would grow crazily.

What I'm doing:

Fixes #issue

What type of PR is this:

  • BugFix
  • Feature
  • Enhancement
  • Refactor
  • UT
  • Doc
  • Tool

Does this PR entail a change in behavior?

  • Yes, this PR will result in a change in behavior.
  • No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

  • Interface/UI changes: syntax, type conversion, expression evaluation, display information
  • Parameter changes: default values, similar parameters but with different default values
  • Policy changes: use new policy to replace old one, functionality automatically enabled
  • Feature removed
  • Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

  • I have added test cases for my bug fix or my new feature
  • This pr needs user documentation (for new or modified features or behaviors)
    • I have added documentation for my new feature or new function
  • This is a backport pr

Bugfix cherry-pick branch check:

  • I have checked the version labels which the pr will be auto-backported to the target branch
    • 3.3
    • 3.2
    • 3.1
    • 3.0
    • 2.5

@satanson satanson requested a review from a team as a code owner October 30, 2024 08:51
Copy link

[Java-Extensions Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[FE Incremental Coverage Report]

pass : 0 / 0 (0%)

Copy link

[BE Incremental Coverage Report]

pass : 3 / 3 (100.00%)

file detail

path covered_line new_line coverage not_covered_line_detail
🔵 be/src/exprs/like_predicate.cpp 3 3 100.00% []

error << "Invalid hyperscan expression: " << std::string(slice.data, slice.size) << ": "
auto chopped_size = std::min<size_t>(slice.size, 64);
auto ellipsis = (chopped_size < slice.size) ? "..." : "";
error << "Invalid hyperscan expression: " << std::string(slice.data, chopped_size) << ellipsis << ": "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
error << "Invalid hyperscan expression: " << std::string(slice.data, chopped_size) << ellipsis << ": "
error << "Invalid hyperscan expression: " << std::string_view(slice.data, chopped_size) << ellipsis << ": "

std::string_view might be lightweight in such case.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is a low-frequency executing code.

@satanson satanson merged commit e95d0be into StarRocks:main Oct 31, 2024
55 checks passed
ZiheLiu pushed a commit to ZiheLiu/starrocks that referenced this pull request Oct 31, 2024
@satanson
Copy link
Contributor Author

satanson commented Nov 1, 2024

@Mergifyio backport branch-3.3

Copy link
Contributor

mergify bot commented Nov 1, 2024

backport branch-3.3

✅ Backports have been created

@satanson
Copy link
Contributor Author

satanson commented Nov 1, 2024

https://github.com/Mergifyio backport branch-3.2

Copy link
Contributor

mergify bot commented Nov 1, 2024

backport branch-3.2

✅ Backports have been created

@satanson
Copy link
Contributor Author

satanson commented Nov 1, 2024

https://github.com/Mergifyio backport branch-3.1

Copy link
Contributor

mergify bot commented Nov 1, 2024

backport branch-3.1

✅ Backports have been created

@satanson
Copy link
Contributor Author

satanson commented Nov 1, 2024

https://github.com/Mergifyio backport branch-3.0

mergify bot pushed a commit that referenced this pull request Nov 1, 2024
…an error (#52467)

Signed-off-by: satanson <[email protected]>
(cherry picked from commit e95d0be)
@satanson
Copy link
Contributor Author

satanson commented Nov 1, 2024

https://github.com/Mergifyio backport branch-2.5

Copy link
Contributor

mergify bot commented Nov 1, 2024

backport branch-3.0

✅ Backports have been created

Copy link
Contributor

mergify bot commented Nov 1, 2024

backport branch-2.5

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Nov 1, 2024
…an error (#52467)

Signed-off-by: satanson <[email protected]>
(cherry picked from commit e95d0be)
mergify bot pushed a commit that referenced this pull request Nov 1, 2024
…an error (#52467)

Signed-off-by: satanson <[email protected]>
(cherry picked from commit e95d0be)
mergify bot pushed a commit that referenced this pull request Nov 1, 2024
…an error (#52467)

Signed-off-by: satanson <[email protected]>
(cherry picked from commit e95d0be)
mergify bot pushed a commit that referenced this pull request Nov 1, 2024
…an error (#52467)

Signed-off-by: satanson <[email protected]>
(cherry picked from commit e95d0be)
wanpengfei-git pushed a commit that referenced this pull request Nov 1, 2024
wanpengfei-git pushed a commit that referenced this pull request Nov 1, 2024
wanpengfei-git pushed a commit that referenced this pull request Nov 1, 2024
wanpengfei-git pushed a commit that referenced this pull request Nov 1, 2024
wanpengfei-git pushed a commit that referenced this pull request Nov 1, 2024
renzhimin7 pushed a commit to renzhimin7/starrocks that referenced this pull request Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants