can't find schema when insert into ON DUPLICATE

[SunRunAway]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. What did you do?
   If possible, provide a recipe for reproducing the error.

drop table a;
drop table b;
create table a (x int);
create table b (x int ,y int);
insert into a select x from b ON DUPLICATE KEY UPDATE 
a.x=b.y;

2. What did you expect to see?

Query OK, 0 rows affected (0.00 sec)
Records: 0  Duplicates: 0  Warnings: 0

3. What did you see instead?

ERROR 1054 (42S22): Unknown column 'b.y' in 'field list'

4. What version of TiDB are you using (tidb-server -V or run select tidb_version(); on TiDB)?

[SunRunAway]

Another case:

1. What did you do?
   If possible, provide a recipe for reproducing the error.

drop table a;
drop table b;
create table a (x int);
create table b (x int);
insert into a select if(x, 1, 2) x from b ON DUPLICATE KEY UPDATE a.x=b.x;

2. What did you expect to see?

Query OK, 0 rows affected (0.01 sec)
Records: 0  Duplicates: 0  Warnings: 0

3. What did you see instead?

ERROR 1054 (42S22): Unknown column 'b.x' in 'field list'

[SunRunAway]

Better to fix it in v3.0.9

[SunRunAway]

Due to "The feature can not work in its main workflow", I change the severity to cirtical.

[ti-srebot]

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)

MySQL's behavior is somehow against logic. So TiDB wasn't compatible with it before.

2. Symptom (optional)

The SQL mentioned in the issue will report error.

3. All Trigger Conditions (optional)

See issue body.

4. Workaround (optional)

No.

5. Affected versions

[v4.0.1:v4.0.10], unreleased

6. Fixed versions

master

[tiancaiamao]

Rejected in 4.0.16 bug triage