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

[BugFix] fix no matching function error in array_contains/array_position (backport #51835) #51879

Open
wants to merge 1 commit into
base: branch-3.3
Choose a base branch
from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 14, 2024

Why I'm doing:

What I'm doing:

Fixes https://github.com/StarRocks/StarRocksTest/issues/8662

introduced by: #50912

taking array_contains as an example,
before #50912, array_contains had only one function signature array_contains(ANY_ARRAY,ANY_ELEMENT). in #50912, I added many type-specialized function signatures for it and special handings in normalizeDecimalArgTypes.
image

FunctionAnalyzer will determine whether to follow the logic of getDecimalV3Function based on whether the arguments contain decimal type.
image

image

array_contains is a bit special. for array_contains(array<array<decimal>>, array<decimal>), the second argument will hit the check logic of argumentTypeContainDecimalV3 and go to getDecimalV3Function. since array<decimal> and decimal don't have a common type, the subsequent processing will cause errors.

In fact, this situation should not follow the processing logic of getDecimalV3Function, so I made a special judgment in this pr to solve this problem.

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

This is an automatic backport of pull request #51835 done by [Mergify](https://mergify.com). ## Why I'm doing:

What I'm doing:

Fixes https://github.com/StarRocks/StarRocksTest/issues/8662

introduced by: #50912

taking array_contains as an example,
before #50912, array_contains had only one function signature array_contains(ANY_ARRAY,ANY_ELEMENT). in #50912, I added many type-specialized function signatures for it and special handings in normalizeDecimalArgTypes.
image

FunctionAnalyzer will determine whether to follow the logic of getDecimalV3Function based on whether the arguments contain decimal type.
image

image

array_contains is a bit special. for array_contains(array<array<decimal>>, array<decimal>), the second argument will hit the check logic of argumentTypeContainDecimalV3 and go to getDecimalV3Function. since array<decimal> and decimal don't have a common type, the subsequent processing will cause errors.

In fact, this situation should not follow the processing logic of getDecimalV3Function, so I made a special judgment in this pr to solve this problem.

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

…ion (#51835)

Signed-off-by: silverbullet233 <[email protected]>
(cherry picked from commit 8cc2ae2)
Copy link

sonarcloud bot commented Oct 14, 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.

1 participant