ctubbsii commented on PR #5439: URL: https://github.com/apache/accumulo/pull/5439#issuecomment-2770002658
I'd have reservations further coupling the accumulo-cluster script to our code. It really exists as a reference implementation for cluster management and shouldn't be tightly coupled. However, this feature could still be supported if we add sufficient primitives to our API, or admin utility or to the accumulo-cluster script. For example, the accumulo-cluster script could have a command to list the configured servers, and the accumulo admin command can show the ones that are running and provide a means to kill them. Basically, I think adding more primitives supports this use case and others, whereas adding a high level prune command only satisfies this one use case, and possibly does so by creating more dependencies between the accumulo-cluster script and our non-public endpoints into our code. As it stands, I'm leaning towards suggesting that we replace the cluster config parser in our code with `yq` as a dependency of accumulo-cluster script, so we have less coupling between the code and this script. I'm not in a rush to make that change, but I would like to avoid adding further couplings. -- 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]
