planner: dynamic partition prune should be aware of the caller‘s on-missing action

[AilinKid]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

set global tidb_partition_prune_mode='dynamic';

drop table tt1;
drop table tt2;

CREATE TABLE tt1 (
    id INT NOT NULL,
    listid INT,
    name varchar(10)
)

PARTITION BY LIST (listid) (
    PARTITION p1 VALUES IN (1),
    PARTITION p2 VALUES IN (2),
    PARTITION p3 VALUES IN (3),
    PARTITION p4 VALUES IN (4)
);

CREATE TABLE tt2 (
    id INT NOT NULL,
    listid INT
);

create index idx_listid on tt1(id,listid);
create index idx_listid on tt2(listid);

delete from tt1;
delete from tt2;

insert into tt1 values(1,1,1);
insert into tt1 values(2,2,2);
insert into tt1 values(3,3,3);
insert into tt1 values(4,4,4);
insert into tt2 values(1,1);
insert into tt2 values(2,2);
insert into tt2 values(3,3);
insert into tt2 values(4,4);
insert into tt2 values(5,5);

analyze table tt1;
analyze table tt2; 

explain analyze
select /*+ inl_join(tt1)*/ count(*) from tt2
left join tt1 on tt1.listid=tt2.listid and tt1.id=tt2.id; ERROR 1526 (HY000): Table has no partition for value 5 

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

locate partition error doesn't mean it's indeed an error.
Under the index lookup scenario, the on-missing action of locate partition should return no rows infetchInnerResuts back to the caller IndexLookUpJoin

3. What did you see instead (Required)

locate partition error

4. What is your TiDB version? (Required)

all versions, even master