[DISCUSS] Refactoring IoTDB to eliminate the singleton pattern

Hi all, So, one thing that has always been bothering me a bit with respect to the IoTDB code-base, was the usage of the singleton pattern. Even if it simplifies composition of a project, it comes with quite some severe disadvantages. In my last PR I tried refactoring the usage of singletons to

Re: [PR] chore(deps-dev): Bump org.apache.flink:flink-shaded-zookeeper-3 from 3.8.1-17.0 to 3.8.3-18.0 [iotdb-extras]

dependabot[bot] commented on PR #3: URL: https://github.com/apache/iotdb-extras/pull/3#issuecomment-2263558328 Superseded by #14. -- 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

Re: [PR] chore(deps-dev): Bump org.apache.flink:flink-shaded-zookeeper-3 from 3.8.1-17.0 to 3.8.3-18.0 [iotdb-extras]

dependabot[bot] closed pull request #3: chore(deps-dev): Bump org.apache.flink:flink-shaded-zookeeper-3 from 3.8.1-17.0 to 3.8.3-18.0 URL: https://github.com/apache/iotdb-extras/pull/3 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

[PR] chore(deps-dev): Bump org.apache.flink:flink-shaded-zookeeper-3 from 3.8.1-17.0 to 3.8.3-19.0 [iotdb-extras]

dependabot[bot] opened a new pull request, #14: URL: https://github.com/apache/iotdb-extras/pull/14 Bumps org.apache.flink:flink-shaded-zookeeper-3 from 3.8.1-17.0 to 3.8.3-19.0. [![Dependabot compatibility

[PR] Fixed the issue where the Grafana plugin does not display data [iotdb-extras]

CloudWise-Lukemiao opened a new pull request, #13: URL: https://github.com/apache/iotdb-extras/pull/13 Fixed the issue where the Grafana plugin does not display data when there is no time value -- This is an automated message from the Apache Git Service. To respond to the message, please

答复: How to handle the internal and external IPs of Data-Nodes?

Hi， After careful consideration, it seems that relying solely on the nodeId would be a more viable option 发件人: Christofer Dutz 日期: 星期五, 2024年7月26日 14:55 收件人: dev@iotdb.apache.org 主题: AW: How to handle the internal and external IPs of Data-Nodes? Well, I think I’m going to do it my usuall

AW: How to handle the internal and external IPs of Data-Nodes?

Well, I think I’m going to do it my usuall way If a discussion dries up here … I’ll do what I proposed as I didn’t read any opposing opinion before and not after, so I’ll treat this as consent. If objections come after … I’ll just add stuff back. Wouldn’t be my time wasted ;-) Chris Von:

AW: How to handle the internal and external IPs of Data-Nodes?

But having another look at the documentation at https://iotdb.apache.org/UserGuide/V1.0.x/Cluster/Cluster-Maintenance.html#show-datanode-information The NodeID displayed in “show cluster” (datanodes have ids 3,4 and 5) seem to be different from the ones shown in show datanodes (1 and 2) Also

AW: How to handle the internal and external IPs of Data-Nodes?

Comparing the output of them, I think deleting nodes only by ID is probably the best option. Perhaps in a second PR we could update the output of show datanodes to include the InternalAddress and InternalPort? I probably also should check if removing config nodes via ID works … because

答复: How to handle the internal and external IPs of Data-Nodes?

Hi Chris Perhaps more often than not, show clusters are used? Best Xuan Wang 发件人: Christofer Dutz 日期: 星期四, 2024年7月25日 15:31 收件人: dev@iotdb.apache.org 主题: AW: How to handle the internal and external IPs of Data-Nodes? Hi all, In that case we would need to show the internal ip

AW: How to handle the internal and external IPs of Data-Nodes?

Hi all, In that case we would need to show the internal ip in the show datanodes command, right? Or would we simply expect the user to know the internal IP of the datanode he wants to remove? Chris Von: Wang Critas Datum: Donnerstag, 25. Juli 2024 um 08:16 An: dev@iotdb.apache.org Betreff:

AW: How to handle the internal and external IPs of Data-Nodes?

That would be my favorite option … to directly show the internal and external ip/ports. With my fix in the PR, removing by ID is now possible, so yes … then we should remove the option to use the Ip+port notation. Chris Von: 乔嘉林 Datum: Donnerstag, 25. Juli 2024 um 03:05 An:

答复: How to handle the internal and external IPs of Data-Nodes?

Hi Why not use nodeId or internalAddress:internalPort for unified behavior Remove ConfigNode through nodeId or internalAddress:internamPort Best Xuan Wang 发件人: Xinyu Tan 日期: 星期四, 2024年7月25日 12:26 收件人: dev@iotdb.apache.org 主题: Re: How to handle the internal and external IPs

Re: How to handle the internal and external IPs of Data-Nodes?

Hi, chris +1 for identifying nodes solely by nodeid Best Xinyu Tan On 2024/07/24 14:33:20 Christofer Dutz wrote: > Hi all, > > I’m currently working on https://github.com/apache/iotdb/pull/12914 > > Here one of the problems was, that in a cluster with 3 datanodes, where the

Re: How to handle the internal and external IPs of Data-Nodes?

Hi, Could we list both two addresses? One for internal and another for client connection. As for removing a datanode, maybe prividing the nodeid is enough. Jialin > From: "Christofer Dutz" > Date: Wed, Jul 24, 2024, 22:37 > Subject: How to handle the internal and external IPs of Data-Nodes?

How to handle the internal and external IPs of Data-Nodes?

Hi all, I’m currently working on https://github.com/apache/iotdb/pull/12914 Here one of the problems was, that in a cluster with 3 datanodes, where the dn_rpc_address is set to 0.0.0.0, the command “show datanodes” lists each node with an address of 0.0.0.0. So, if someone wants to remove a

Re: [PR] chore(deps): Bump braces from 3.0.2 to 3.0.3 in /connectors/grafana-plugin [iotdb-extras]

HTHou merged PR #12: URL: https://github.com/apache/iotdb-extras/pull/12 -- 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. To unsubscribe, e-mail:

[PR] chore(deps): Bump braces from 3.0.2 to 3.0.3 in /connectors/grafana-plugin [iotdb-extras]

dependabot[bot] opened a new pull request, #12: URL: https://github.com/apache/iotdb-extras/pull/12 Bumps [braces](https://github.com/micromatch/braces) from 3.0.2 to 3.0.3. Commits https://github.com/micromatch/braces/commit/74b2db2938fad48a2ea54a9c8bf27a37a62c350d;>74b2db2

Re: [PR] chore(deps): Bump golang.org/x/net from 0.17.0 to 0.23.0 in /connectors/grafana-plugin [iotdb-extras]

HTHou merged PR #7: URL: https://github.com/apache/iotdb-extras/pull/7 -- 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. To unsubscribe, e-mail: dev-unsubscr...@iotdb.apache.org

Re: [PR] chore(deps): Bump ws from 7.5.9 to 7.5.10 in /connectors/grafana-plugin [iotdb-extras]

HTHou merged PR #9: URL: https://github.com/apache/iotdb-extras/pull/9 -- 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. To unsubscribe, e-mail: dev-unsubscr...@iotdb.apache.org

Re: [PR] chore(deps): Bump fast-loops from 1.1.3 to 1.1.4 in /connectors/grafana-plugin [iotdb-extras]

HTHou merged PR #11: URL: https://github.com/apache/iotdb-extras/pull/11 -- 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. To unsubscribe, e-mail:

[DISCUSS] Next steps with predictive test selection?

Hi all, I know the IoTDB build is taking longer and longer to run. Also is IoTDB the unfortunately one of the biggest consumer of GitHub Actions compute resources at Apache (At least we were pointed out as such at Community Over Code Bratislava). There I worked together with some folks from

AW: AW: AW: AW: Possible pattern for reducing the negative effects of using singletons and improving testability

Ok … guess my numbers were not 100% correct. It was pointed out that it says: “that you are part of” at the top of the page. So from all project that I’m a committer of (it shows 9) IoTDB consumed 95% of the resources. Not quite as bad as I thought at first, but still not good. Chris Von:

AW: AW: AW: AW: Possible pattern for reducing the negative effects of using singletons and improving testability

And just so you know how huge this problem is: https://infra-reports.apache.org/#ghactions For all non-members, that don’t have access to that resource: It shows how much of the GitHub Actions resources each project is using. Apache IoTDB is currently using 95% of all GitHub Actions resources,

AW: AW: AW: AW: Possible pattern for reducing the negative effects of using singletons and improving testability

I think for some tests, it might be worth migrating them back from an IT to an UT. I’m currently trying to get resource-consumption stats from infra and wanted to start finding out which are our most “expensive” Its and possibly start a discussion on converting them to unit-tests. Right now, it

Re: AW: AW: AW: Possible pattern for reducing the negative effects of using singletons and improving testability

Certainly, I am not actually expecting a really perfect solution, just hoping when someone else sees this discussion, he may provide a better trade-off. And as I have said, I am happy with both solutions, as long as they can get rid of the singletons. Mocking is helpful in tests. But the

How to use the new streaming queries?

Hi all, I am currently working a bit on my little PLC4X + IoTDB Home automation project which I plan to use to make little videos about IoTDB features. Right now, what I’m trying to figure out, is how can I define a streaming query? I have multiple devices, each one providing numerous

AW: AW: AW: Possible pattern for reducing the negative effects of using singletons and improving testability

Hi Tian, I think – as usual – there probably is no perfect solution. I guess it comes down to deciding which things you are willing to do in order to solve some other problems on the other side. I personally think our biggest problem right now (At least this is what’s making my Life a lot

Re: AW: AW: Possible pattern for reducing the negative effects of using singletons and improving testability

A template (or util) method can provide basic contexts, and the developers just need to override the parts they need (of course they should know which parts they need). In the constructor-way, the developer should know what instances they will use, create them, and pass them to the

AW: AW: Possible pattern for reducing the negative effects of using singletons and improving testability

However, then you need to construct these contexts with loads of parameters for unit tests … I personally don’t think passing in explicitly what you need into a constructor is bad. So, if you have this service that you want to test: How can you tell the developer writing the test which services

Re: AW: Possible pattern for reducing the negative effects of using singletons and improving testability

Yes, maybe we could have leveled context like DataNodeContext, DataRegionContext, TsFileProcessorContext... and put the former singletons in these contexts. This may avoid constructors with dozens of parameters. Tian Jiang | | Tian Jiang | | jt2594...@163.com | Replied Message |

AW: Possible pattern for reducing the negative effects of using singletons and improving testability

Ideally, we could inspect the usages of the constructors using the singletons and apply the same pattern there. Once all usages have been migrated that way, we could even eliminate the Singleton-using constructor. In the end getting a system for which we can finally write sensible unit-tests

AW: Possible pattern for reducing the negative effects of using singletons and improving testability

Ok … So, as there was no objection here, I’ll trat that as consensus and I’ll just do this for every component that I touch and hereby need to write tests for. Chris Von: Christofer Dutz Datum: Montag, 15. Juli 2024 um 11:49 An: dev@iotdb.apache.org Betreff: Possible pattern for reducing the

RE: [DISCUSS] Clean handling of issues in CLIs?

> -Original Message- > From: Christofer Dutz > Sent: Monday, July 15, 2024 1:03 PM > To: dev@iotdb.apache.org > Subject: [DISCUSS] Clean handling of issues in CLIs? > > Hi all, > > also while working on the DataNodeServerCli I noticed that we don't > actually handle how CLIs deal with

[DISCUSS] Clean handling of issues in CLIs?

Hi all, also while working on the DataNodeServerCli I noticed that we don’t actually handle how CLIs deal with issues correctly. While in most case in case of a successful operation we return a code of 0, we don’t consequently do this in case of issues. Sometimes we return -1 or other cases,

Possible pattern for reducing the negative effects of using singletons and improving testability

Hi all, I am currently working on some functions and when writing tests for these, I had problems sensibly testing things, as the singletons were preventing that. As I mentioned before … I consider the usage of singletons the probably worst design decision done in IoTDBs core. Even if it

AW: Re:[DISCUSS] Design of Table Model Permission Feature

Apache email lists (except security lists) don’t accept attachments. Chris Von: Colin_Lee Datum: Donnerstag, 11. Juli 2024 um 06:40 An: dev@iotdb.apache.org Betreff: Re:[DISCUSS] Design of Table Model Permission Feature Soory that It appears that there has been an unexpected issue; the

Re:[DISCUSS] Design of Table Model Permission Feature

Soory that It appears that there has been an unexpected issue; the attachment was not accepted and forwarded by the mail server. You can get the design document from the URL bellow. Design_zh: https://apache-iotdb.feishu.cn/docx/BYwjdvm73ohwgmxQldbcQ9w8nTy?from=from_copylink Design_eng:

Re:[DISCUSS] Design of Table Model Permission Feature

I have re-attached the email attachment. At 2024-07-11 12:24:40, "Colin_Lee" wrote: Hello everyone, I'm recently working on the functionality related to table model permissions. At present, there is already a basic table model permission design document that is open for

[DISCUSS] Design of Table Model Permission Feature

Hello everyone, I'm recently working on the functionality related to table model permissions. At present, there is already a basic table model permission design document that is open for discussion. This document has referenced the design ideas of permissions in the mainstream relational

[PR] chore(deps): Bump fast-loops from 1.1.3 to 1.1.4 in /connectors/grafana-plugin [iotdb-extras]

dependabot[bot] opened a new pull request, #11: URL: https://github.com/apache/iotdb-extras/pull/11 Bumps [fast-loops](https://github.com/robinweser/fast-loops) from 1.1.3 to 1.1.4. Commits See full diff in https://github.com/robinweser/fast-loops/commits;>compare view

Enable C# Client to Intialize and Reconnect with Multiple Node Urls

Hi, I have implemented an interface within the C# client that supports initialization using multiple Node URLs. Additionally, the reconnection method has been enhanced to select one of the various Nodes for reestablishing a connection. For further details, please refer to PR[1]. Would someone be

RE: Re:Integrating UDF Library and Grafana (conf update) in Docker

Miaohsh wrote: > The rest service currently does not support hot loading. After modifying > the configuration, the iotdb service needs to be restarted before it can > be used > Thank you for the confirmation. I just wanted to check I was understanding the IoTDB configuration mechanisms

[ANNOUNCE] Apache IoTDB 1.3.2 released

The Apache IoTDB team is pleased to announce the release of Apache IoTDB 1.3.2. Apache IoTDB (Database for Internet of Things) is an IoT native database with high performance for data management and analysis, deployable on the edge and the cloud. Apache IoTDB 1.3.2 is the latest version of the

[RESULT][VOTE] Release Apache IoTDB 1.3.2

Hi all, The release is approved by accepting 3 +1 votes: 3 from PMC members, Qingxin Feng, Christofer Dutz, Jialin Qiao. Vote threads: https://lists.apache.org/thread/svdkp2gqy960t9svpmygp4hdjcdnoswo Thanks, Haonan Hou

Re: [VOTE] Apache IoTDB 1.3.2 RC1 release

Hi, +1 (binding) The source release: apache headers [ok] signatures and hashes [ok] LICENSE and NOTICE [ok] no jar files [ok] The binary distribution: version number in CLI [ok] signatures and hashes [ok] start in mac, jdk8 [ok] Thanks, Jialin Qiao Christofer Dutz 于2024年6月28日周五 19:15写道： > >

AW: [VOTE] Apache IoTDB 1.3.2 RC1 release

+1 (binding) Chris [OK] Download all staged artifacts under the url specified in the release vote email. [OK] Verify the signature is correct. [OK] Check if the signature references an Apache email address. [OK] Verify the SHA512 hashes. [OK] Unzip the archive. [OK] Verify the existence of

回复: [VOTE] Apache IoTDB 1.3.2 RC1 release

Hello all : +1 The binary distribution: version number in CLI [ok] start in CentOS7, jdk11 [ok] performance verification passed: [ok] ### Server Configurations ###// CPU=16 Memory=32G Disk=1.8T HDD Ethernet=1000Mbit

Re: Allow the client with python 3.6 to use IoTDB

Ok, this PR has been merged. Best, Haonan On 2024/06/24 14:19:36 Haonan Hou wrote: > Hi, > > The current python client of IoTDB requires the python version >= 3.7. > However, I met some applications running on some old platforms which only > support python 3.6, and I found it is easy to make

[VOTE] Apache IoTDB 1.3.2 RC1 release

Hi all, Apache IoTDB 1.3.2 has been staged under [2] and it’s time to vote on accepting it for release. All Maven artifacts are available under [1]. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass. Release tag: v1.3.2 Hash

Integrating UDF Library and Grafana (conf update) in Docker

Hi, After some successful experiments I would like to enable the optional data quality UDF Library and support Grafana in the COVESA Central Data Service Playground (CDSP). Functions like the LTTB Triangle sampling are very useful in automotive use-cases. I have some questions related to UDF

Allow the client with python 3.6 to use IoTDB

Hi, The current python client of IoTDB requires the python version >= 3.7. However, I met some applications running on some old platforms which only support python 3.6, and I found it is easy to make the adaption. Here is the PR[1]. In this PR, I also added a CI with python 3.6 and it can work

RE: Introducing Apache IoTDB use in COVESA Central Data Service Playground

Hi, Thank you both, for the encouragement and the offers of support. > -Original Message- > From: Jialin Qiao > Sent: Tuesday, June 18, 2024 9:50 AM > To: dev@iotdb.apache.org > Subject: Re: Introducing Apache IoTDB use in COVESA Central Data Service > Playground > > Hi, > > Glad to

Re: Apply for a development platform account

Hi yuyong, Welcome to IoTDB Community, I've already approved your jira account application. It didn't work? Best regards, -- Yuan Tian On Fri, Jun 21, 2024 at 4:50 PM 喻勇 <1471335...@qq.com.invalid> wrote: > Dear IoTDB PMC: > > Greetings! > > I am yuyong,I am currently a

Apply for a development platform account

Dear IoTDB PMC: Greetings! I am yuyong,I am currently a graduate student at Chongqing University of Posts and Telecommunications, and I am currently very interested in IoTDB and would like to contribute my part in it. I am passionate about participating in the open source community. After

答复: Recover/Reset Root Password?

In addition, in versions after 1.3.1, if the file and the files in snapshot are deleted, restarting will automatically generate a file containing the default password, without the need to find the file and put it in it. And you can also take a look at the relevant source code 发件人: Wang Critas

答复: Recover/Reset Root Password?

Hi Trevor The method you mentioned is feasible, but it is important to note that the corresponding IoTDB version of the file needs to be matched. Additionally, the cluster needs to be restarted. This operation is quite dangerous. It is recommended to make a backup in advance, and the best

Re: Introducing Apache IoTDB use in COVESA Central Data Service Playground

Hi, Glad to see the integration! Welcome and feel free to ask :D Jialin Qiao Pengcheng Zheng 于2024年6月15日周六 04:38写道： > > Hi Stephen, > > Very exciting project! > > Thanks for sharing the details of COVESA/CDSP. I remember that you asked > some questions in Slack several months ago, and seems

Recover/Reset Root Password?

Hello Is there a process to recover or reset the root user password? For example, if a customer forgets their root user password. Is it possible to replace the "root.profile" file under data/confignode/system/users with the default? Would this work? Thanks  Trevor Hart

Introducing Apache IoTDB use in COVESA Central Data Service Playground

Hi, As suggested in the wiki I am introducing myself and a new OSS project using Apache IoTDB. My name is Stephen Lawrence from Renesas Electronics and I work in the COVESA[1] open automotive alliance. COVESA is focused on developing common approaches and technologies for connected vehicles,

Re: IoTDB quarter report (2024 Q2)

> And I have something more to add: Cool. I will add these activities. --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Pengcheng Zheng 于2024年6月12日周三 16:16写道： > > Hi Xiangdong, > > Great ;) > > And I have something more to add: > - on

Re: IoTDB quarter report (2024 Q2)

Hi Xiangdong, Great ;) And I have something more to add: - on 2024-04-09, IoTDB was presented at the JavaLand Summit in Germany. The talk was given by Christofer Dutz. [1] - on 2024-06-03, IoTDB was presented in 2 talks at CommunityOverCode EU. The talks were given by Christofer Dutz and Julian

Introduction of Enhanced Load Functionality with Multi-Drive Support

Hello everyone, My name is Itami Sho, a contributor to IoTDB, and I am excited to share with you a recent enhancement I have implemented in our Load functionality. This optimization introduces support for multiple drive letters during the second phase of Load functionality to store TsFile

Re: ALIGN BY DEVICE: the data types of the same measurement column should be the same across devices.

Ah that is great to hear! Thank you! Thanks  Trevor Hart On Wed, 12 Jun 2024 13:50:43 +1200 Jialin Qiao wrote --- Hi, We just changed the default infer type of integer and floating to DOUBLE [1], it will be released in 1.3.2. For <=1.3.1, you could explicitly set this to

Re: ALIGN BY DEVICE: the data types of the same measurement column should be the same across devices.

Hi, We just changed the default infer type of integer and floating to DOUBLE [1], it will be released in 1.3.2. For <=1.3.1, you could explicitly set this to DOUBLE. [1] https://github.com/apache/iotdb/pull/12223 Jialin Qiao Trevor Hart 于2024年6月12日周三 06:41写道： > > Hello Team > > > > I have a

Re: IoTDB quarter report (2024 Q2)

Looks good! Jialin Qiao Xiangdong Huang 于2024年6月12日周三 09:11写道： > > Hi all, > > This is the draft of IoTDB quarter report > > ## Description: > The mission of Apache IoTDB is the creation and maintenance of software > related > to an IoT native database with high performance for data management

IoTDB quarter report (2024 Q2)

Hi all, This is the draft of IoTDB quarter report ## Description: The mission of Apache IoTDB is the creation and maintenance of software related to an IoT native database with high performance for data management and analysis ## Project Status: Current project status: Ongoing with high

ALIGN BY DEVICE: the data types of the same measurement column should be the same across devices.

Hello Team I have a customer using my application with IoTDB 1.3.0 in the backend. Auto create schema is enabled as there is no fixed template. Multiple devices are pushing data to IotDB. I have seen some ALIGN BY DEVICE queries fail with the error in the subject ie ALIGN BY DEVICE:

Re: AW: version about odbc

There is another example of the rest-client-c-example without the pom.xml that demonstrate how to use rest api with c language. Should we consider it as document example, or a "compilable" example? I prefer it is a compilable module and I think it is possible to add a pom.xml and make it as a

AW: Session API issues

I guess the simplest solution would simply be to return an error if not all paths in the query are valid. Right now I added a check on the client side that throws an exception if the size of the paths is different from that of the fields. Chris Von: Christofer Dutz Datum: Sonntag, 9. Juni

Session API issues

Hi all, I have been playing around with the session API and have been stumbling into some pits, that I think would be worth addressing. The biggest issue I have had recently is using the executeAggregationQuery method, passing in pairs of queries and aggregations. However, I noticed that if

AW: version about odbc

The ODBC is not really a “compilable” example. It contains a description how you can use a commercial product to wrap our JDBC driver in order to produce an ODBC driver. Also does it contain a compilable C# project file, that demonstates the usage of the ODBC API. However even if the example

version about odbc

Hi all, I found that in master branch, we've already upgraded the version to 1.3.3-SNAPSHOT, but the examples about odbc module is missed? [image: image.png] Best regards, - Yuan Tian

Re: Prepare releasing 1.3.2?

Ok, the version of master branch has updated to 1.3.3-SNAPSHOT. Once Ratis 3.1.0 released, I'll prepare the rc/1.3.2 branch. Best, Haonan On 2024/06/03 02:07:55 Xinyu Tan wrote: > Hi haonan > > +1 for bumping the version of master branch to 1.3.3-SNAPSHOT. > > As for the 1.3.2 release,

Re: [Proposal] New Consensus Protocals for IoTDB DataRegion

Dear Junzhi Peng and Sicheng Yu, Thank you for sharing the exciting news about the new consensus protocols, FastIoTConsensus and IoTV2Consensus. Your efforts and contributions to improving the IoTDB project are greatly appreciated. We look forward to exploring these new features and providing

Re: [Proposal] Device Level TTL for IoTDB

Hi Peichen I'm very excited to see the implementation of device-level TTL. Before your work, if users wanted to set different TTLs for different devices, they had to model them into many databases, which was very inconvenient. After your work, users can set different TTLs within a single

Re: [Proposal] Device Level TTL for IoTDB

Hi Peichen I'm very excited to see the implementation of device-level TTL. Before your work, if users wanted to set different TTLs for different devices, they had to model them into many databases, which was very inconvenient. After your work, users can set different TTLs within a single

Re: [Proposal] New Consensus Protocals for IoTDB DataRegion

Hi, Junzhi I'm very pleased to see that you and Sicheng Yu are leading the design and development of FastIoTConsensus and IoTV2Consensus. From designing a unified consensus algorithm framework, integrating the strong consistency consensus algorithm Ratis, to self-designing the weak consistency

Re: [Proposal] New Consensus Protocals for IoTDB DataRegion

Hi, Junzhi I'm very pleased to see that you and Sicheng Yu are leading the design and development of FastIoTConsensus and IoTV2Consensus. From designing a unified consensus algorithm framework, integrating the strong consistency consensus algorithm Ratis, to self-designing the weak consistency

Re: [DISCUSS] GH Actions optimizations

ok..., if so, I think it's really nice. On Wed, Jun 5, 2024 at 8:28 PM Christofer Dutz wrote: > Also is the settings currently done that it only skips any tests in > non-master branches … so if there’s a PR on a branch, that will be > optimized, but every commit going back to master should have

AW: [DISCUSS] GH Actions optimizations

Also is the settings currently done that it only skips any tests in non-master branches … so if there’s a PR on a branch, that will be optimized, but every commit going back to master should have all tests run. Chris Von: Christofer Dutz Datum: Mittwoch, 5. Juni 2024 um 14:22 An:

AW: [DISCUSS] GH Actions optimizations

Well even with the re-run option still failures get counted and a dashboard like this: https://ge.apache.org/scans/tests?search.rootProjectNames=*IoTDB*=Europe%2FBratislava=FLAKY Is a lot better than having to continuously go back to your PRs and click on “re-run failed tests” Chris Von: Yuan

Re: [RESULT] [VOTE] Release IotDB-Tools: Thrift artifacts (for Apache Thrift 0.20.0)

Thank Chris! Jialin Qiao Christofer Dutz 于2024年6月4日周二 17:28写道： > > Ok … artifacts should be available … > > Chris > > Von: Christofer Dutz > Datum: Dienstag, 4. Juni 2024 um 11:26 > An: dev@iotdb.apache.org > Betreff: [RESULT] [VOTE] Release IotDB-Tools: Thrift artifacts (for Apache > Thrift

[DISCUSS] GH Actions optimizations

At today’s sessions at community over code EU in a session about “Apache build observability” we got a little spotlight on IoTDB. The develocity folks pointed out Apache IoTDB as being the one Apache project that provides the biggest room for improvement by enabling some of their

AW: [RESULT] [VOTE] Release IotDB-Tools: Thrift artifacts (for Apache Thrift 0.20.0)

Ok … artifacts should be available … Chris Von: Christofer Dutz Datum: Dienstag, 4. Juni 2024 um 11:26 An: dev@iotdb.apache.org Betreff: [RESULT] [VOTE] Release IotDB-Tools: Thrift artifacts (for Apache Thrift 0.20.0) So, the vote passes with 7 +1 votes at least 5 I could verify as binding

[RESULT] [VOTE] Release IotDB-Tools: Thrift artifacts (for Apache Thrift 0.20.0)

So, the vote passes with 7 +1 votes at least 5 I could verify as binding votes. In the future, it would be great if people would add their name/apacheId etc. to the votes to make it easier to verify and count for the RM. Releasing the maven artifacts right away. Thanks for all those who voted.

Re: [VOTE] Release IotDB-Tools: Thrift artifacts (for Apache Thrift 0.20.0)

Yeah.. Currently at community over code... Was planning on doing this in a break today. Gesendet von Outlook für Android From: Haonan Hou Sent: Monday, June 3, 2024 4:11:04 AM To: dev@iotdb.apache.org Subject: Re: [VOTE] Release

Re: [Proposal] New Consensus Protocals for IoTDB DataRegion

Hello Junzhi, I would like to extend my heartfelt thanks to you and Sicheng Yu for your FastIoTConsensus and IoTV2Consensus protocols. It is a significant step forward for IoTDB. I am well aware that the existing IoTConsensus has been performing exceptionally well in most scenarios, yet it

Re: [Proposal] Merge configuration files to iotdb-system.properties

Hi, Most of the changes in this PR are to modify the configuration file itself and some script tools that will read the configuration file. Codes for accessing the options are not merged. Best regards, Wenwei Shu Christofer Dutz 于2024年6月1日周六 15:32写道： > However, > > I think it would be good If

[Proposal] New Consensus Protocals for IoTDB DataRegion

Hello everyone, I'm Junzhi Peng, a new contributor to IoTDB. Recently, I and Sicheng Yu, the committer of IoTDB, have implemented two new consensus protocols on DataRegion based on IoTDB Pipe framework: FastIoTConsensus and IoTV2Consensus, and we are excited to share with you this new feature.

Re: [Proposal] Merge configuration files to iotdb-system.properties

Hi, > I think it would be good If the code for accessing the options would not be > merged. +1, I think the code is not merged in Wenwei's PR. Jialin Qiao Caiyin Yang 于2024年6月3日周一 10:27写道： > > Hi Xinyu, > > If that's the case, then this merge seems to be very user-friendly. > > Best > Caiyin

Re: [Proposal] Load Tsfile Functionality Optimisation

Hi Xiangzhi, Thank you for sharing your work on the load tsfile feature. I am currently working on the Load function as well, and I have a question for you. Have you considered enhancing the Load function directly within the core code, rather than relying on the script to load tsfiles one by

Re: [Proposal] Active metaData Query

Hi ITAMI, ‘Active’ refers to the data that can be seen by query in the specified time range, which you can also understand as data that has been written in the specified time and not deleted later. Best CaiyinYang > 2024年6月3日 15:40，ITAMI SHO 写道： > > question

Re: [Proposal] Active metaData Query

Hi Caiyin, Thank you for your contribution, I have a question regrading the definition of active metadata. Could you please provide more details on what constitutes “active metadata” in this context? Understanding this definition better will help us utilize this new feature! Thank you again

Re: Canonical the semantics of auto create schema function

Hi Yongzao Dan, Thank you for your recent contribution to the Apache IoTDB community. Your work on clarifying the semantics of the auto-create schema function and addressing the associated issues has been incredibly valuable to IoTDB. Your dedication and attention to detail are greatly

[Proposal] Active metaData Query

Hello everyone, I'm Caiyin Yang, a contributor to IoTDB. I have implemented an active metadata query feature in IoTDB in the past few months, which is an extension based on the original *SHOW/COUNT DEVICES/TIMESERIES *SQL. You only need to specify the time condition in the SQL statement (*for

Re: [Proposal] Add the feature of importing and exporting metadata by CSV file

Hi Rong Li, This is a great new feature. Thank you for working on this. Registering metadata is usually a time-consuming operation in the case of massive sequences. I am curious about the efficiency of importing and exporting metadata. Have the scripts been tested on large-scale sequences? If

Re: [Proposal] Merge configuration files to iotdb-system.properties

Hi Xinyu, If that's the case, then this merge seems to be very user-friendly. Best Caiyin Yang Xinyu Tan 于2024年6月3日周一 10:22写道： > Hi, Caiyin > > Following Wenwei's work, we plan to introduce an > iotdb-system.properties.template file that will contain all configuration > items, relevant

Re: Canonical the semantics of auto create schema function

Hi rongzhao It's really cool that with this change we're able to provide more explicit auto-creation semantics to our users. Best -- Xinyu Tan On 2024/06/01 04:43:05 Yongzao Dan wrote: > Hi everyone, > > > I'm Yongzao Dan, a committer in the Apache IoTDB community. > > >

Re: [Proposal] Merge configuration files to iotdb-system.properties

Hi, Caiyin Following Wenwei's work, we plan to introduce an iotdb-system.properties.template file that will contain all configuration items, relevant comments, and optional settings, similar to the latest user configuration manual. In the future, the iotdb-system.properties file will only

  1   2   3   4   5   6   7   8   9   10   >