Re: The structure of distribution

2022-07-11 Thread Haonan Hou 
Hi,
 
I have a question.

If users would like to extend a standalone IoTDB to cluster, is it a good idea 
that
separate standalone and datanode to different directories?

Best,
Haonan Hou

> On Jul 12, 2022, at 9:19 AM, SpriCoder  wrote:
> 
> Finally, From my perspective, one possible structure like below:
> 
> 
> .
> ├── LICENSE
> ├── NOTICE
> ├── README.md
> ├── README_ZH.md
> ├── RELEASE_NOTES.md
> ├── sbin
> │ ├── start-cli.bat
> │ └── start-cli.sh
> 
> ├── confignode
> │ ├── conf
> │ │ ├── confignode-env.bat
> │ │ ├── confignode-env.sh
> │ │ ├── iotdb-confignode.properties
> │ │ ├── iotdb-metric.yml
> │ │ ├── jmx.access
> │ │ ├── jmx.password
> │ │ ├── logback-tool.xml
> │ │ └── logback.xml
> │ └── sbin
> │   ├── remove-confignode.sh
> │   ├── start-confignode.bat
> │   ├── start-confignode.sh
> │   ├── stop-confignode.bat
> │   └── stop-confignode.sh
> ├── datanode
> │ ├── conf
> │ │ ├── datanode-env.bat
> │ │ ├── datanode-env.sh
> │ │ ├── iotdb-datanode.properties
> │ │ ├── iotdb-metric.yml
> │ │ ├── iotdb-rest.properties
> │ │ ├── jmx.access
> │ │ ├── jmx.password
> │ │ ├── logback-tool.xml
> │ │ └── logback.xml
> │ └── sbin
> │   ├── remove-datanode.bat
> │   ├── remove-datanode.sh
> │   ├── start-datanode.bat
> │   ├── start-datanode.sh
> │   ├── stop-datanode.bat
> │   └── stop-datanode.sh
> ├── standalone
> │ ├── conf
> │ │ ├── datanode-env.bat
> │ │ ├── datanode-env.sh
> │ │ ├── iotdb-datanode.properties
> │ │ ├── iotdb-metric.yml
> │ │ ├── iotdb-rest.properties
> │ │ ├── jmx.access
> │ │ ├── jmx.password
> │ │ ├── logback-tool.xml
> │ │ └── logback.xml
> │ └── sbin
> │   ├── start-new-server.bat
> │   ├── start-new-server.sh
> │   ├── start-server.bat
> │   ├── start-server.sh
> │   ├── stop-server.bat
> │   └── stop-server.sh
> 
> ├── docs
> ├── grafana-metrics-example
> ├── lib
> ├── licenses
> └── tools
> 
> 
> 
> 
> 
> 
> 
> --Original--
> From: 
>"SpriCoder"
> 
>  Date:Tue, Jul 5, 2022 05:54 PM
> To:"dev" 
> Subject:The structure of distribution
> 
> 
> 
> Hi all,
> 
> Currently, we have confignode and datanode folder in the distribution. Which 
> has conf, sbin, and will store the default folder of data and system. And 
> there is a need to refactor distribution structure.
> 
> I think there are two choices:
> 
> 1. remove the confignode and datanode folder, and combine their script and 
> configuration files into the conf and sbin under the root. In this way all 
> folder generated by confignode will be put into config folder, and all folder 
> generated by confignode will be put into data folder.
> 
> 2. use confignode and datanode folder to manage their script and 
> configuration files, like: confignode/sbin, confignode/conf, datanode/sbin, 
> datanode/conf, etc. In this way all folder generated by confignode will be 
> put into confignode folder and all folder generated by datanode will be put 
> into datanode folder.
> 
> 
> 
> 
> What's your opinion? Looking forward to your reply.
> 
> 
> Best,
> 
> ---
> 
> Hongyin Zhang

Re:The structure of distribution

2022-07-11 Thread SpriCoder 
Finally, From my perspective, one possible structure like below:


.
?? LICENSE
?? NOTICE
?? README.md
?? README_ZH.md
?? RELEASE_NOTES.md
?? sbin
?? ?? start-cli.bat
?? ?? start-cli.sh

?? confignode
?? ?? conf
?? ?? ?? confignode-env.bat
?? ?? ?? confignode-env.sh
?? ?? ?? iotdb-confignode.properties
?? ?? ?? iotdb-metric.yml
?? ?? ?? jmx.access
?? ?? ?? jmx.password
?? ?? ?? logback-tool.xml
?? ?? ?? logback.xml
?? ?? sbin
??   ?? remove-confignode.sh
??   ?? start-confignode.bat
??   ?? start-confignode.sh
??   ?? stop-confignode.bat
??   ?? stop-confignode.sh
?? datanode
?? ?? conf
?? ?? ?? datanode-env.bat
?? ?? ?? datanode-env.sh
?? ?? ?? iotdb-datanode.properties
?? ?? ?? iotdb-metric.yml
?? ?? ?? iotdb-rest.properties
?? ?? ?? jmx.access
?? ?? ?? jmx.password
?? ?? ?? logback-tool.xml
?? ?? ?? logback.xml
?? ?? sbin
??   ?? remove-datanode.bat
??   ?? remove-datanode.sh
??   ?? start-datanode.bat
??   ?? start-datanode.sh
??   ?? stop-datanode.bat
??   ?? stop-datanode.sh
?? standalone
?? ?? conf
?? ?? ?? datanode-env.bat
?? ?? ?? datanode-env.sh
?? ?? ?? iotdb-datanode.properties
?? ?? ?? iotdb-metric.yml
?? ?? ?? iotdb-rest.properties
?? ?? ?? jmx.access
?? ?? ?? jmx.password
?? ?? ?? logback-tool.xml
?? ?? ?? logback.xml
?? ?? sbin
??   ?? start-new-server.bat
??   ?? start-new-server.sh
??   ?? start-server.bat
??   ?? start-server.sh
??   ?? stop-server.bat
??   ?? stop-server.sh

?? docs
?? grafana-metrics-example
?? lib
?? licenses
?? tools







--Original--
From:   
 "SpriCoder"

[BUILD-UNSTABLE]: Job 'IoTDB/IoTDB-Pipe/master [master] [643]'

2022-07-11 Thread Apache Jenkins Server 
BUILD-UNSTABLE: Job 'IoTDB/IoTDB-Pipe/master [master] [643]':

Check console output at "https://ci-builds.apache.org/job/IoTDB/job/IoTDB-Pipe/job/master/643/;>IoTDB/IoTDB-Pipe/master
 [master] [643]"

[IOTDB-3800]Add Node Type Column to 'SHOW CHILD PATHS' query

2022-07-11 Thread Zhou Yifu 
Hi all,

Currently our show child paths query looks a bit disordered and it seems that 
only the paths names can be displayed. Besides these paths names, we cannot 
know more detail about this paths’ meanings in our metadata model. So I want to 
add one more ‘node type’ column to it and also can be sorted by these types.
How about node type is:
root -> sg internal -> storage group -> internal -> device -> timeseries
Feel free to discuss here, Thanks a lot!

Regards,
Yifu Zhou