You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@iotdb.apache.org by "Yuan Tian (Jira)" <ji...@apache.org> on 2022/02/11 03:02:00 UTC
[jira] [Created] (IOTDB-2533) change max_deduplicated_path_num does not take effect
Yuan Tian created IOTDB-2533:
--------------------------------
Summary: change max_deduplicated_path_num does not take effect
Key: IOTDB-2533
URL: https://issues.apache.org/jira/browse/IOTDB-2533
Project: Apache IoTDB
Issue Type: Bug
Components: Core/Query
Reporter: Yuan Tian
Assignee: Yuan Tian
If we change meta_data_cache_enable=false and change max_deduplicated_path_num in iotdb-engine.properties meanwhile, max_deduplicated_path_num won't take effect.
Change the following two items in iotdb-engine.properties
```
meta_data_cache_enable=false
max_deduplicated_path_num=2
```
And then start iotdb-server.
And then execute the following commands
```
insert into root.sg.d1(time,s1) values(1,1);
insert into root.sg.d1(time,s2) values(1,1);
insert into root.sg.d1(time,s3) values(1,1);
select last s1, s2, s3 from root.sg.d1;
```
We expect to get `PathNumOverLimitException: Too many paths in one query!` exeception, because we already change max_deduplicated_path_num to 2, but it can be executed successfully.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)