-
Notifications
You must be signed in to change notification settings - Fork 246
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
TISPARK-21 delete redundant dag column that affects index single read #304
Conversation
/run-all-tests |
assert(execDBTSAndJudge("select b from prefix where b >= \"bbc\" and b < \"bbd\"")) | ||
assert(execDBTSAndJudge("select c, b from prefix where b = \"bb\" and b < \"bbc\"")) | ||
} | ||
|
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.
Prefix index tests have been moved to prefixIndexTestSuite
.
/run-all-tests |
PTAL @Novemser @ilovesoup |
@@ -123,7 +123,7 @@ class BaseTiSparkSuite extends QueryTest with SharedSQLContext { | |||
|
|||
def execDBTSAndJudge(str: String, skipped: Boolean = false): Boolean = | |||
try { | |||
compResult(querySpark(str), queryTiDB(str)) | |||
compResult(querySpark(str), queryTiDB(str), str.contains(" order by ")) |
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.
missed isOrdered
check here which results in test case failure.
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
The additional dag column when field is empty seems unnecessary. It also causes index single read to require a non index nor handle column.
Delete its usage to fix index single read.