EmmyMiao87 opened a new issue #3771:
URL: https://github.com/apache/incubator-doris/issues/3771
**Describe the bug**
When user query the UNIQUE table, the new mv selector could not select
correct indexId.
The warning log like
```
2020-06-04 14:45:58,361 WARN 101
[OlapScanNode.updateScanRangeInfoByNewMVSelector():232] Using the old scan
range info instead of the new one. The key type of table is aggregated., The
new selected index id 0, pre aggregation tag true, reason null. The old
selected index
id 213392 pre aggregation tag false reason No AggregateInfo
```
**To Reproduce**
Steps to reproduce the behavior:
1. Create a unique table
```
create table unique_table(k1 int, k2 int) UNIQUE KEY(k1) distributed by
hash(k1) properties("replication_num" = "1");
```
2. insert value
```
insert into unique_table values(1,1);
```
3. query
```
select * from unique_table;
```
4. see fe.log
```
2020-06-04 15:18:01,420 WARN 131
[OlapScanNode.updateScanRangeInfoByNewMVSelector():232] Using the old scan
range info instead of the new one. The key type of table is aggregated., The
new selected index id 0, pre aggregation tag true, reason null. The old selecte
d index id 10007 pre aggregation tag false reason No AggregateInfo
```
**Expected behavior**
No warning log, the new selector choose the correct index id which is same
as the rollup selector.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
