+1 for [ Option 1] Putting bat and sh scripts together is not very intuitive, and [Option1] like Kafka[1].
[1]: https://github.com/apache/kafka/tree/trunk/bin Best regards, ----------------------- Xuan Wang 发件人: 王艺儒 <yiru.w...@timecho.com> 日期: 星期三, 2025年4月16日 17:07 收件人: dev <dev@iotdb.apache.org> 主题: [DISCUSS]Adjustments to sbin and tools Scripts Hi all, As the number of scripts continues to grow, the current count within a single sbin directory has reached as high as 27. Moreover, these scripts are scattered across various projects such as datanode, confignode, cli, and node-commons, making the search and maintenance of scripts quite inconvenient. Therefore, we plan to migrate the scripts in the next version, with the main content as follows: • Script Central Management: Migrate scripts scattered across different projects to the scripts/sbin and scripts/tools directories under the root directory. • Script Functional Classification: Categorize and move scripts to different files or subdirectories based on their functionality. For frequently used scripts, their current locations will be preserved to minimize the impact on existing workflows. • Cross-Platform Script Separation: Due to the excessive number of scripts, we are considering separating Windows and Unix scripts and have proposed the following four options: • Option 1: Create a Windows subfolder under the sbin directory (sbin, sbin/windows). • Option 2: Create a Windows folder parallel to the sbin directory (sbin, sbin-windows). • Option 3: Distinguish during packaging to generate installation packages for different platforms (apache-iotdb-xxx-SNAPSHOT-all-bin-windows, apache-iotdb-xxx-SNAPSHOT-all-bin-unix). • Option 4: Maintain the status quo for the time being (mixed Windows and Unix). We sincerely invite community members to vote on these options, with a limit of two votes per person. Your choice is very important to us and will directly affect the implementation of the script migration plan.
