dlmarion commented on PR #5599:
URL: https://github.com/apache/accumulo/pull/5599#issuecomment-2949190146
> However, I don't think we should add all this to the usage.
If the consensus is to not add this extra information to the usage, then I'm
good with that.
> I think it is misleading because it is noisy, incorrectly implies a
comprehensive list, and has little value. It is also likely to be hard to keep
current as we add new properties and server types in future.
I added the extra information to the usage because of the comments from
#4976. I think it has value, because it was asked for, but I'll let others
chime in. The usage printed to the screen is based off the Property enum, so
this should automatically update as properties are added to existing prefixes.
New server types and new prefixes might require this to be updated.
In my experience relying solely on the documentation and/or release notes
for information doesn't work. People either don't read them, or only read them
once. For someone that is managing a system and needs to override a property
quickly, going to the documentation might not be an option. Providing some
context-aware help is user-friendly, like bash auto-completion, for example.
> I think the use of the -o option is likely to be rare, and is usually not
the best choice in many scenarios.
I do agree that the use of the `-o` option is likely rare now, but I'm not
sure that will be the case in the future. For example, the `-a` property that
has been replaced by the `-o` bind address property is almost required when
running Accumulo processes in Kubernetes (and maybe Docker).
--
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]
