You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@iotdb.apache.org by Minghui Liu <li...@gmail.com> on 2023/02/15 01:29:57 UTC

[Discussion] Deprecate configuration parameter `max_deduplicated_path_num`

In version 1.0, we have designed a finer query memory control
mechanism, which can ensure that the query will not be executed when
there are too many queried time series. Therefore, we no longer need
this parameter.

I plan to deprecate this parameter in the next version. What's your opinion?

Regards,
-----------------------------------
Minghui Liu
School of Software, Tsinghua University

刘明辉
清华大学 软件学院

Re: [Discussion] Deprecate configuration parameter `max_deduplicated_path_num`

Posted by 谭新宇 <10...@qq.com.INVALID>.
Awesome！

It's very exciting to see that this parameter can be deprecated, as I thought it would be annoying for users to expose the exception that the maximum path number cannot exceed this `max_deduplicated_path_num`!

Thanks
——————————————
Xinyu Tan

> 2023年2月15日 09:29，Minghui Liu <li...@gmail.com> 写道：
> 
> In version 1.0, we have designed a finer query memory control
> mechanism, which can ensure that the query will not be executed when
> there are too many queried time series. Therefore, we no longer need
> this parameter.
> 
> I plan to deprecate this parameter in the next version. What's your opinion?
> 
> Regards,
> -----------------------------------
> Minghui Liu
> School of Software, Tsinghua University
> 
> 刘明辉
> 清华大学 软件学院

回复: [Discussion] Deprecate configuration parameter `max_deduplicated_path_num`

Posted by 冯 庆新 <qi...@hotmail.com>.
Hi,

+ 1 for deprecate this parameter
But does the new version return the correct results by splitting the query into fewer series through memory control?
Or just reject the query to indicate that there is insufficient memory?

B.R.
Qingxin Feng

发件人: Minghui Liu<ma...@gmail.com>
发送时间: 2023年2月15日 9:31
收件人: dev@iotdb.apache.org<ma...@iotdb.apache.org>
主题: [Discussion] Deprecate configuration parameter `max_deduplicated_path_num`

In version 1.0, we have designed a finer query memory control
mechanism, which can ensure that the query will not be executed when
there are too many queried time series. Therefore, we no longer need
this parameter.

I plan to deprecate this parameter in the next version. What's your opinion?

Regards,
-----------------------------------
Minghui Liu
School of Software, Tsinghua University

刘明辉
清华大学 软件学院