Hi all,

I did a bit of poking at bin/solr command to remove a lot of the 
parameter/option checking from the bin/solr script to the Java code as part if 
SOLR-16876,

For most of the options (see 
https://github.com/apache/solr/blob/main/solr/bin/solr#L1021) it’s very 
straightforward, just pass them all into the Java code.   However, the one 
sticking point is that we seem to have some logic for parsing the Solr Server 
directory (the -d parameter) that is rather opaque to me, and I’m not sure if 
it’s easy to translate into Java code, see 
https://github.com/apache/solr/blob/main/solr/bin/solr#L1070.   

Then, further down we have some more parsing logic in 
https://github.com/apache/solr/blob/main/solr/bin/solr#L1115.  

I’d love someone to take a looksee at some of that logic.  If anyone is 
interested in a bit of a logic puzzle, I’d love some help on this. 

I have a PR with a bats test for validating the lifecycle of using the auth 
command: https://github.com/apache/solr/pull/1833. 



Eric


_______________________
Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | 
http://www.opensourceconnections.com <http://www.opensourceconnections.com/> | 
My Free/Busy <http://tinyurl.com/eric-cal>  
Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 
<https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw>
    
This e-mail and all contents, including attachments, is considered to be 
Company Confidential unless explicitly stated otherwise, regardless of whether 
attachments are marked as such.

Reply via email to