-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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 Attempt to unlock lock, not locked by current locker in mv refresh #51884
[BugFix] Fix Attempt to unlock lock, not locked by current locker in mv refresh #51884
Conversation
fe/fe-core/src/main/java/com/starrocks/sql/analyzer/PlannerMetaLocker.java
Outdated
Show resolved
Hide resolved
fe/fe-core/src/main/java/com/starrocks/common/util/concurrent/lock/Locker.java
Outdated
Show resolved
Hide resolved
@@ -70,7 +70,7 @@ public class MvNormalizePredicateRule extends NormalizePredicateRule { | |||
@Override | |||
public ScalarOperator visitCompoundPredicate(CompoundPredicateOperator predicate, | |||
ScalarOperatorRewriteContext context) { | |||
Map<String, ScalarOperator> sorted = Maps.newTreeMap(String.CASE_INSENSITIVE_ORDER); | |||
Map<String, ScalarOperator> sorted = Maps.newTreeMap(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if changed, the column name would be case-sensitive, which means behavior change ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add more comments, PTAL.
fe/fe-core/src/main/java/com/starrocks/common/util/concurrent/lock/Locker.java
Outdated
Show resolved
Hide resolved
Signed-off-by: shuming.li <[email protected]>
6c86f61
to
0a2d301
Compare
Signed-off-by: shuming.li <[email protected]>
|
[Java-Extensions Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
[FE Incremental Coverage Report]✅ pass : 6 / 6 (100.00%) file detail
|
[BE Incremental Coverage Report]✅ pass : 0 / 0 (0%) |
@Mergifyio backport branch-3.3 |
✅ Backports have been created
|
…mv refresh (#51884) Signed-off-by: shuming.li <[email protected]> (cherry picked from commit a1a3130) # Conflicts: # fe/fe-core/src/main/java/com/starrocks/common/util/concurrent/lock/Locker.java # fe/fe-core/src/test/java/com/starrocks/planner/MaterializedViewTest.java
…mv refresh (backport #51884) (#51965) Signed-off-by: shuming.li <[email protected]> Co-authored-by: shuming.li <[email protected]>
…mv refresh (backport #51884) (#51965) Signed-off-by: shuming.li <[email protected]> Co-authored-by: shuming.li <[email protected]> (cherry picked from commit 5387fe8)
…mv refresh (StarRocks#51884) Signed-off-by: shuming.li <[email protected]>
@mergify cherry-pick branch-3.2 |
❌ Sorry but I didn't understand the command. Please consult the commands documentation 📚. |
@mergify backport branch-3.2 |
@mergify backport branch-3.1 |
✅ Backports have been created
|
✅ Backports have been created
|
…mv refresh (#51884) Signed-off-by: shuming.li <[email protected]> (cherry picked from commit a1a3130) # Conflicts: # fe/fe-core/src/main/java/com/starrocks/common/util/concurrent/lock/Locker.java # fe/fe-core/src/test/java/com/starrocks/planner/MaterializedViewTest.java
…mv refresh (#51884) Signed-off-by: shuming.li <[email protected]> (cherry picked from commit a1a3130) # Conflicts: # fe/fe-core/src/main/java/com/starrocks/common/util/concurrent/lock/Locker.java # fe/fe-core/src/test/java/com/starrocks/planner/MaterializedViewTest.java
…mv refresh (backport #51884) (#52647) Signed-off-by: shuming.li <[email protected]> Co-authored-by: shuming.li <[email protected]>
…mv refresh (backport #51884) (#52648) Signed-off-by: shuming.li <[email protected]> Co-authored-by: shuming.li <[email protected]>
…mv refresh (StarRocks#51884) Signed-off-by: shuming.li <[email protected]> Signed-off-by: zhiminr.ren <[email protected]>
Why I'm doing:
Fix two bugs in using mv:
col in (upper('a'), lower('a')
;What I'm doing:
Maps.newTreeMap()
instead ofCASE_INSENSITIVE_ORDER
to avoid this.Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist:
Bugfix cherry-pick branch check: