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

TiFlash report BadRequest when push timestamp down. #22917

Closed
LittleFall opened this issue Feb 24, 2021 · 5 comments · Fixed by pingcap/tiflash#1472
Closed

TiFlash report BadRequest when push timestamp down. #22917

LittleFall opened this issue Feb 24, 2021 · 5 comments · Fixed by pingcap/tiflash#1472
Assignees
Labels
severity/moderate sig/execution SIG execution type/bug This issue is a bug.

Comments

@LittleFall
Copy link
Contributor

Bug Report

1. Minimal reproduce step (Required)

CREATE TABLE t(a timestamp);
alter table t set tiflash replica 1;
insert into t values (current_timestamp());

SELECT /*+ read_from_storage(tiflash[t])*/ count(*) FROM t WHERE a = (SELECT max(a) FROM t);

2. What did you expect to see? (Required)

mysql> SELECT /*+ read_from_storage(tikv[t])*/ count(*) FROM t WHERE a = (SELECT max(a) FROM t);
+----------+
| count(*) |
+----------+
|        1 |
+----------+
1 row in set (0.06 sec)

3. What did you see instead (Required)

SELECT /*+ read_from_storage(tiflash[t])*/ count(*) FROM t WHERE a = (SELECT max(a) FROM t);
ERROR 1105 (HY000): [FLASH:Coprocessor:BadRequest] Invalid MySQL Time literal tp: MysqlTime
val: "\031\250\360\214T\000\000\000"
sig: Unspecified
field_type {
  tp: 7
  flag: 129
  flen: 19
  decimal: 0
  collate: 63
  charset: "binary"
}

4. What is your TiDB version? (Required)

mysql> select tidb_version();
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| tidb_version()                                                                                                                                                                                                                                                                                                          |
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Release Version: v4.0.0-beta.2-2153-g461cae1
Edition: Community
Git Commit Hash: 461cae15a755c72fb587c97414348832035c4972
Git Branch: HEAD
UTC Build Time: 2021-02-22 02:26:55
GoVersion: go1.13.7
Race Enabled: false
TiKV Min Version: v3.0.0-60965b006877ca7234adaced7890d7b029ed1306
Check Table Before Drop: false |
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
1 row in set (0.01 sec)
@LittleFall LittleFall added the type/bug This issue is a bug. label Feb 24, 2021
@LittleFall
Copy link
Contributor Author

/severity moderate

@LittleFall
Copy link
Contributor Author

/sig execution

@LittleFall
Copy link
Contributor Author

/assign @LittleFall

@LittleFall LittleFall changed the title TiFlash report BadRequest when push timestamp literal down. TiFlash report BadRequest when push timestamp down. Feb 24, 2021
@cyliu0 cyliu0 added the sig/execution SIG execution label Feb 24, 2021
@LittleFall
Copy link
Contributor Author

/assign @windtalker

@ti-srebot
Copy link
Contributor

ti-srebot commented Mar 1, 2021

Please edit this comment or add a new comment to complete the following information

Not a bug

  1. Remove the 'type/bug' label
  2. Add notes to indicate why it is not a bug

Duplicate bug

  1. Add the 'type/duplicate' label
  2. Add the link to the original bug

Bug

Note: Make Sure that 'component', and 'severity' labels are added
Example for how to fill out the template: #20100

1. Root Cause Analysis (RCA) (optional)

2. Symptom (optional)

3. All Trigger Conditions (optional)

4. Workaround (optional)

5. Affected versions

[v4.0.0:v4.0.11]

6. Fixed versions

master

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/moderate sig/execution SIG execution type/bug This issue is a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants