Re: Introducing a memory control mechanism during the query planning stage #12573

Hi, lanyu and hongying I am very pleased to see that you have made breakthroughs in memory management, and I am so eager to learn memory control techniques from you! Best ——— Xinyu Tan > 2024年5月23日 15:24，Yuan Tian 写道： > > Hi hongying, > > sure, feel free to discuss anything about any

Re: Keeping an eye on Jenkins

Hi, Chris Late last year, we spent several months fixing the unstable UT/IT to get Github CI and Jenkins CI up and running. After our efforts, both of them should be stable for several weeks. However, the last few months have brought some new CI instability issues, this time a rat file, and

Re: Keeping an eye on Jenkins

Hi, Chris Late last year, we spent several months fixing the unstable UT/IT to get Github CI and Jenkins CI up and running. After our efforts, both of them should be stable for several weeks. However, the last few months have brought some new CI instability issues, this time a rat file, and

Re: [DISCUSS] Please don't write output of tests to the root directory of a module.

o, it could have been that this was all ok till a new version of rat was > being used. > > However that doesn’t change the fact that generating test output anywhere > outside the target directory is really a bad idea. > > Chris > > Von: 谭新宇 <1025599...@qq.com.INVALID>

Re: [DISCUSS] Please don't write output of tests to the root directory of a module.

Hi, Chris I checked the UT and it looks like it hasn't been changed in two or three years. We have been running into unexpected errors in the Jenkins environment, such as data cleaning problems, which could lead to similar errors. Naturally, the license header check is also included in Github

Re: Fixing flaky tests?

Hi Chris, I deeply apologize for the instability of replicateUsingWALTest. The test failures are occurring due to the frequent start and stop of the thrift server in the consensus module tests, which can lead to some tests being unable to bind to the socket during startup and resulting in

Re: [DISCUSS] Updating to a newer Thrift version?

Hi, Chris In the latest version of thrift, there are some improvements we'd like to make, For example, https://issues.apache.org/jira/browse/THRIFT-5502 will down-cycled "connection reset" warn logs. +1 for upgrading thrift. Thanks Xinyu Tan > 2023年7月31日 19:50，Christofer Dutz

Re: 如何设置10720和10750端口的监听地址

Hi, This should be caused by confingode's cn_internal_address(in confignode-properties) set to 0.0.0.0, which needs to be set to the actual Intranet ip, and it does not support modification at present. If you need to change it, you can configure cn_internal_address to hostname and then modify

Re: New subscriber Shuolin Li's self-introduction

Welcome ShuoLin ! Looking forward to your contribution! Xinyu Tan > 2023年7月4日 16:44，shuolin li 写道： > > Dear IoTDB team, > > My name is Shuolin Li, or call me Colin Li. > > I have been working for two years on a distributed database, a commercial > version of Apache HAWQ. I

Re: Remove UserGuide before 0.13 from website

Hi, +1 for removing old docs Thanks -- Xinyu Tan > 2023年2月23日 18:30，Jialin Qiao 写道： > > Hi, > > There are 8 versions UserGuide on our website[1], the old versions are > hardly used anymore. > > I prefer to remove the history versions before 0.13 (not include). > > [1]

Re: [Discussion] Deprecate configuration parameter `max_deduplicated_path_num`

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 写道： > >

Re: new committer: Haiming Zhu

Congratulations Haiming! Xinyu Tan > 2022年12月28日 23:31，Jialin Qiao 写道： > > Hi, > > The Project Management Committee (PMC) for Apache IoTDB > has invited Haiming Zhu to become a committer and we are pleased > to announce that he has accepted. > > Being a committer enables easier

Re: new committer: Rongzhao Chen

Congratulations rongzhao! Xinyu Tan > 2023年1月4日 17:46，HW-Chao Wang <576749...@qq.com.INVALID> 写道： > > Congratulations, Rongzhao has made outstanding contributions to the > confignode architecture and code > > > > ---Original--- > From: "Jialin Qiao" Date: Wed, Jan 4, 2023 17:10 PM

Re: new PMC: Chao Wang

Congratulation! Thanks —— Xinyu Tan > 2022年12月16日 16:17，Xin Wang 写道： > > Congrats Chao! > > Zhou Yifu 于2022年12月15日周四 17:19写道： > >> Congrats! Well-deserved! >> >> Thanks, >> Yifu Zhou >> >> 获取 Outlook for iOS >> >> 发件人: Jialin

Re: Quarterly report of IoTDB

Hi, I seem to have found a typo. > On 2022-12-03 and 04, the community hosted Apache IoTDB ecosystem summit, > there are more than 60 audiences watch the summit online. Maybe it’s 60k audiences, not 60 audiences. Best — Xinyu Tan > 2022年12月15日 14:26，Xiangdong Huang 写道： > > Hi all, >

Re: [ANNOUNCE] Apache IoTDB 1.0.0 released

Amazing team work! This is a new beginning for IoTDB! Thanks — Xinyu Tan > 2022年12月5日 22:27，HW-Chao Wang <576749...@qq.com.INVALID> 写道： > > Congratulations, we are looking forward to this version！ > > > > > ---Original--- > From: "Haonan Hou" Date: Mon, Dec 5, 2022 20:46 PM > To:

Re: Rename MultiLeaderConsensus to IoTConsensus

Hi， For these two reasons, I strongly agree with the name change. Users do not need to know the name of MultiLeader which is strongly related to the implementation. However, as the consensus module is currently an extensible framework, more consensus algorithms may be integrated in the

Re: What is the next architecture of IoTDB?

There's been a lot of talk about cluster new architectures, and stability has been a problem for a long time. For the former, I agree that we need to summarize our experience and discuss the problems with our current architecture and possible improvements. But it's not enough just to point out

Re: discuss why we have to replace hostname to ip in the cluster module

Hi, +1 for hostname. This makes it easier to migrate the data from the failed node and start it at another one. And I don't think it makes much sense to allow users to intermix hostname and IP in seed_nodes in current implementation. Best — Xinyu Tan > 在 2021年8月26日，上午9:34，Jialin Qiao

Re: ready for release v0.12.2?

Hi, + 1 Best — Xinyu Tan > 在 2021年8月25日，上午9:26，Steve Su 写道： > > Hi, > > +1. > > We have done a lot of work on the stability around the rel/0.12. Looking > forward to the new release! > > Steve Su > Tsinghua University > > -- Original -- > From: "dev"

Re: A cleaner way to construct Session and SessionPool in Java Native API

Great Work JiaJun :) ——— Best, Xinyu Tan > 在 2021年7月8日，下午10:26，Xiangdong Huang 写道： > > Ok. look forward. > (But do not remove stale APIs for compatibility). > > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > >

Re: [VOTE] change release tags from release/{full-version} to v{full-version}

Hi, +1 Best —— Xinyu Tan > 在 2021年1月28日，下午8:24，Houliang Qi 写道： > > +1 > > > Thanks, > --- > Houliang Qi > BONC, Ltd > > > On 01/28/2021 18:12，Jialin Qiao wrote： > > +1 > > -- > Jialin Qiao > School of Software, Tsinghua University > > 乔嘉林 > 清华大学

Re: new committer: Xinyu Tan

Hi, Thanks for your encouragement ! Hope the cluster version can be more stable and efficient under our efforts. Best — Xinyu Tan > 在 2020年12月22日，上午9:06，Houliang Qi 写道： > > Congratulations Xinyu! > > > > > Thanks, > --- > Houliang Qi > BONC, Ltd >

Re: The design doc of [IOTDB-965] add timeout in query

Sorry, as this parameter is configurable, it seems my problem can be solved ~ Then I have no problem with this feature and design~ Best ——— Xinyu Tan > 在 2020年11月26日，下午9:32，Xiangwei Wei 写道： > > If a query takes too much time, we'd better interrupt this query instead of > hanging up the

Re: Support `delete storage group '

日周五 下午10:34写道： > >> Hi, >> >>> So I believe it's better for `delete storage group FullPath` command to >> support wildcard, which can be regarded as `delete storage group >> ` >> >> +1, this is a good function >> >> Thanks, >> -- >&g

Re: Re: [DISCUSS]The cluster version management

Hi, If we decide to release cluster version along with master, it seems useless to checkout out a cluster_release branch. But for the operation of merging the cluster_new branch into the master branch, I will have two questions if we finally decide to do that: 1. I am concerned that some