Filter condition is missing caused wrong result in cached table scanning

[tiancaiamao]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

mysql> create table t (id int, c int);
Query OK, 0 rows affected (0.00 sec)

mysql> insert into t values (3,3), (4,4), (5,5);
Query OK, 3 rows affected (0.00 sec)
Records: 3  Duplicates: 0  Warnings: 0

mysql> alter table t cache;
Query OK, 1 row affected (0.01 sec)

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

mysql>  select id+1, c from t where c = 4;
+------+------+
| id+1 | c    |
+------+------+
|    5 |    4 |
+------+------+
1 row in set (0.00 sec)

3. What did you see instead (Required)

// Before the data is cached, the result is correct....
mysql>  select id+1, c from t where c = 4;
+------+------+
| id+1 | c    |
+------+------+
|    5 |    4 |
+------+------+
1 row in set (0.00 sec)

// Execute it several times, after the data is cached, the result become wrong...
// The filter condition c = 4 doesn't take effect.
mysql>  select id+1, c from t where c = 4;
+------+------+
| id+1 | c    |
+------+------+
|    4 |    3 |
|    5 |    4 |
|    6 |    5 |
+------+------+
3 rows in set (0.00 sec)

4. What is your TiDB version? (Required)

master db3e69e

The bug is introduced by #32139

[tiancaiamao]

Ref #25293

[tiancaiamao]

A non-GA feature and this bug is introduced during developing, no release branchs are affected.