Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
The bin/solr and bin/solr.cmd scripts have taken on a lot of logic that would be easier to maintain if it was instead written in Java code, for a handful of reasons
- Any logic in the control scripts is duplicated in two places by definition.
- Increasing test coverage of this logic would be much easier if it was written in Java.
- Few developers are conversant in both bash and Windows-shell, making editing difficult.
Some sections in these scripts make good candidates for migration to Java. This issue should examine any of these that are brought up. However the biggest and most obvious candidate for migration is the argument parsing, validation, usage/help text, etc. for the commands that don't directly start/stop Solr processes (i.e. the "create", "delete", "zk", "auth", "assert" commands).
Attachments
Attachments
Issue Links
- is a parent of
-
SOLR-15831 Refactor bin/solr and bin/solr.cmd to delegate args parsing and usage help to SolrCLI
- Closed
-
SOLR-11946 Move bin/solr arg-parsing logic to Java
- Closed
- is related to
-
SOLR-7871 Platform independent config file instead of solr.in.sh and solr.in.cmd
- Open
-
SOLR-7043 Refactor SolrCLI, bin\solr, bin\solr.cmd to be more unit-testable and less OS specific
- Closed
-
SOLR-16757 Umbrella Ticket for Revamping Solr CLI's for the Future
- Open