ctubbsii commented on issue #4976: URL: https://github.com/apache/accumulo/issues/4976#issuecomment-2408262531
This was done in #3192 (and in #3197) for 3.0.0, and was documented in the published release notes at https://accumulo.apache.org/release/accumulo-3.0.0/ It was done largely in response to the discussion at https://github.com/apache/accumulo/pull/3189#discussion_r1099138145 as a follow-on to a decision to avoid adding a bunch of options to the ServerOpts in that issue, and instead favoring our published documentation at https://accumulo.apache.org/docs/2.x/configuration/server-properties3 So, this is already documented in the published docs on the website for 3.0, the convenience scripts for launching have been updated to use it automatically, and it was documented in the release notes for 3.0. I'm not sure how often people do `bin/accumulo tserver -?`, but I'd be surprised if users are normally calling `bin/accumulo tserver` directly, instead of through a provided convenience cluster management script, systemd unit, or similar entry point. I think the reasoning for removing it was sound, so I would not want to see it come back. But, I would be in favor of adding a note in the output of `bin/accumulo tserver -?` to document that it will change in a future release, and making it more prominent in the 3.0 release notes. Another option is to add a warning when it is used in 2.1. That might be a bit noisy, though, unless you also backport the new property, so people can migrate away from using `-a` to avoid the warning. I'm not sure how difficult it will be to backport... probably not very difficult, but I'm not sure. -- 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]
