Re: Change rpc_address to internal_address in ConfigNode and refactor show cluster

Agreed with it. The changing of 'rpc_address' and 'rpc_port' for ConfigNodes is reasonable. But if we provide rpc service for ConfigNode in the future, the rpc_address for ConfigNode may be re-enabled again. 冯 庆新 于2022年6月30日周四 11:40写道： > > +1 > > 发件人: Yuan Tian >

Re: [VOTE] Apache IoTDB 0.14.0-preview1 RC1 release

Hi, +1 (binding) The source release: apache headers [ok] signatures and hashes [ok] LICENSE and NOTICE [ok] no jar files [ok] could compile from source: ./mvnw.sh clean install [minor issue with a target file not ignored by apache-rat] The binary distribution: version number in CLI [ok]

回复: Change rpc_address to internal_address in ConfigNode and refactor show cluster

+1 发件人: Yuan Tian 发送时间: 2022年6月30日 11:23 收件人: dev 主题: Re: Change rpc_address to internal_address in ConfigNode and refactor show cluster +1 Best, - Yuan Tian On Thu, Jun 30, 2022 at 9:45 AM Jialin Qiao wrote: > > Hi, > >

Re: Change rpc_address to internal_address in ConfigNode and refactor show cluster

+1 Best, - Yuan Tian On Thu, Jun 30, 2022 at 9:45 AM Jialin Qiao wrote: > > Hi, > > As ConfigNode only serve DataNodes and other ConfigNode. > > The rpc_address in ConfigNode should be internal_address. > The rpc_port in ConfigNode should be internal_port. > > After this, the show

Change rpc_address to internal_address in ConfigNode and refactor show cluster

Hi, As ConfigNode only serve DataNodes and other ConfigNode. The rpc_address in ConfigNode should be internal_address. The rpc_port in ConfigNode should be internal_port. After this, the show cluster function needs to be refactored. Previously, show cluster print the rpc_address of DataNode

Re: [VOTE] Apache IoTDB 0.14.0-preview1 RC1 release

Hi, +1 (binding) The source release: apache headers [ok] signatures and hashes [ok] LICENSE and NOTICE [ok] no jar files [ok] could compile from source: ./mvnw.sh clean install [minor issue with a target file not ignored by apache-rat] The binary distribution: version number in CLI [ok]

[VOTE] Apache IoTDB 0.14.0-preview1 RC1 release

Hi all, Apache IoTDB 0.14.0-preview1 version only contains the new cluster version. Apache IoTDB 0.14.0-preview1 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

Re: support grammar 'HAVING' in IoTDB

Hi, Good catch, in previous `without null any/all`, any stands for `and`(your choice 1); all stands for `or`(your choice 2); I think in our having clause, we can keep consistent with where clause. In our where clause, if you write select s1 from root.sg.* where s1 > 1, we will write it as select

Re: Release of new cluster version

Hi, The releasing of 0.14.0-preview1 is starting. We have checkout a branch rel/0.14.0_preview1 to do the release. Here is the new UserGuide of the cluster: https://iotdb.apache.org/UserGuide/Master/Cluster/Cluster-Concept.html The UserGuide will stay at in progress until the 0.14.0 version is

Re: Rename a parameter in .properties file before releasing

+1 ---Original--- From: "Jialin Qiao"

Re: support grammar 'HAVING' in IoTDB

This is really a good feature! Unlike relational database query, the 'column' name in IoTDB is a string concatenated by the prefix path in FROM clause and the suffix path in SELECT clause. In some cases maybe there are more than 1 output columns. If so, does one simple HAVING clause still work

Re: Rename a parameter in .properties file before releasing

+1 — Jialin Qiao Apache IoTDB PMC Yongzao Dan <532741...@qq.com.invalid> 于2022年6月28日周二 22:28写道： > Hi, > > I want to change a pair of misleading parameter names. > > iotdb-datanode.properties: config_nodes - target_config_nodes > iotdb-confignode.properties:config_nodes -

support grammar 'HAVING' in IoTDB

Hello everyone, We want to support having clause in IoTDB. 1.Background Replace grammar ‘without null any/all()’ to help users easier to understand and use. 2.Specification 2.1Current query grammar selectStatement : TRACING? selectClause intoClause? fromClause whereClause? specialClause?