JackieTien97 opened a new pull request, #18555: URL: https://github.com/apache/iotdb/pull/18555
## Motivation Backport #18552 to `rc/2.0.11` as a follow-up to the already merged #18550, so the Edge distribution includes its own daemon-management and data-cleanup tools. ## Changes - Cherry-pick upstream commit `8c50293d3083b47a110e5c4a9825062b6a2c0c2d`. The change applies without conflicts, and the 10-file patch matches upstream exactly. - Add the Edge systemd daemon script and Unix/Windows cleanup scripts, preserving confirmation, failure propagation, configured-directory handling, and configuration/log files. - Support non-interactive `-f` in the Windows stop script and propagate PowerShell failures. - Package the new tools only in Edge and add the upstream cross-platform ops regression coverage to the Edge CI workflow. ## Validation Validated locally on macOS with JDK 17: - `python3 .github/scripts/test-edge-ops.py`: 24 passed; the native Windows-only test was skipped. - `mvn -B -ntp clean package -pl distribution -am -DskipTests`: all 37 modules passed. - Bash syntax and changed XML checks passed. Verified all six distribution ZIPs and SHA-512 checksums; the three new ops scripts are source-identical and executable (`0755`) in Edge, absent from the other packages, and standalone node ops remain excluded from Edge. - Started the built Edge ZIP in an isolated installation with custom ConfigNode/DataNode directories, a separate DataNode data home, and two absolute data directories outside the installation. Tree and Table create/insert/flush/query operations returned the expected results. - Ran the packaged `destroy-edge.sh -f`; verified JVM termination, PID-file removal, removal of all 14 default/configured test data directories, and preservation of all configuration files and logs. Native Windows execution and real systemd service registration were not run locally. The ops regression suite uses stubbed service commands and is included in both Linux and Windows CI. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
