[Enhancement] Full sort use german string for comparison

[satanson]

Why I'm doing:

Full sort using german string for comparison can accelerate queries if the string-type order-by column has different prefix 4 bytes.

use sv enable_full_sort_use_german_string to control this behavior, it is false in default.

for queries constructed on click_bench as follows

-- Q1
with cte as( select MobilePhoneModel, count(1) over(partition by MobilePhoneModel) as cnt from hits) 
select /*+SET_VAR(enable_full_sort_use_german_string=true)*/ sum(murmur_hash3_32(MobilePhoneModel, cnt)) from cte
-- Q2
with cte as( select URL, count(1) over(partition by URL) as cnt from hits) 
select /*+SET_VAR(enable_full_sort_use_german_string=true)*/ sum(murmur_hash3_32(URL, cnt)) from cte
-- Q3
with cte as( select SearchPhrase, count(1) over(partition by SearchPhrase) as cnt from hits) 
select /*+SET_VAR(enable_full_sort_use_german_string=true)*/ sum(murmur_hash3_32(SearchPhrase, cnt)) from cte
-- Q4
with cte as( select Title, count(1) over(partition by Title) as cnt from hits) 
select /*+SET_VAR(enable_full_sort_use_german_string=true)*/ sum(murmur_hash3_32(Title, cnt)) from cte
-- Q5
with cte as( select Referer, count(1) over(partition by Referer) as cnt from hits) 
select /*+SET_VAR(enable_full_sort_use_german_string=true)*/ sum(murmur_hash3_32(Referer, cnt)) from cte
-- Q6
with cte as( select MobilePhoneModel, SearchPhrase, count(1) over(partition by MobilePhoneModel, SearchPhrase) as cnt from hits) 
select /*+SET_VAR(enable_full_sort_use_german_string=true)*/ sum(murmur_hash3_32(MobilePhoneModel, SearchPhrase, cnt)) from cte
-- Q7
with cte as( select MobilePhoneModel, URL, count(1) over(partition by MobilePhoneModel, URL) as cnt from hits) 
select /*+SET_VAR(enable_full_sort_use_german_string=true)*/ sum(murmur_hash3_32(MobilePhoneModel, URL, cnt)) from cte

The test result

Performances of Q2, Q5, Q7 decrease significantly since the order-by column URL and Referer are almost the same.

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
  • 4.0
  • 3.5
  • 3.4
  • 3.3

[stdpain]

seems unused ?

[silverbullet233]

this len is not necessary?

[satanson]

no overhead

[github-actions]

[Java-Extensions Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[FE Incremental Coverage Report]

❌ fail : 2 / 5 (40.00%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	com/starrocks/qe/SessionVariable.java	2	5	40.00%	[5326, 5327, 5330]

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud