-
Notifications
You must be signed in to change notification settings - Fork 5.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
plan: use Column.UniqueID
in conditionChecker
of ranger (#8236)
#9587
Conversation
/run-all-tests tidb-test=release-2.1 tikv=release-2.1 pd=release-2.1 |
c.Assert(fmt.Sprintf("%s", conds), Equals, tt.accessConds, Commentf("wrong access conditions for expr: %s", tt.exprStr)) | ||
result, err := ranger.BuildColumnRange(conds, new(stmtctx.StatementContext), col.RetType) | ||
c.Assert(err, IsNil) | ||
got := fmt.Sprintf("%v", result) | ||
c.Assert(got, Equals, tt.resultStr, Commentf("different for expr %s, col: %v", tt.exprStr, col)) | ||
} | ||
} | ||
|
||
func (s *testRangerSuite) TestIndexRangeElimininatedProjection(c *C) { |
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.
We should remove this test case, since 2.1 does not have optimization to simplify ifnull()
expression, so this test would fail.
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.
How about keeping the test and modifying the test expect result?
/run-all-tests tidb-test=release-2.1 tikv=release-2.1 pd=release-2.1 |
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.
LGTM
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.
LGTM
cherry-pick #8236