Hi Robert, This issue seems very similar to https://issues.apache.org/jira/browse/SOLR-17457. Are you using Solr 9.7 perhaps?
Looking into the code of 9.7, it seems that the script does add the -scheme flag in the background for you. The help output does not print this option because it was not migrated correctly. There is an ongoing migration of the CLI options, which is probably the root cause. I filed an issue where you can track its progress at https://issues.apache.org/jira/browse/SOLR-17459. Best regards, Christos On Tue, Sep 24, 2024 at 11:23 AM Ehrenleitner Robert Harald < robert.ehrenleit...@plus.ac.at> wrote: > I have set up a new instance of Solr (it is really not the first time I do > this), and right after bin/solr create, I am completely stuck: > > $ bin/solr config --name mysearchindex --solr-url http://localhost:8983< > http://localhost:8983/> --action set-user-property --property > update.autoCreateFields --value false > Failed to parse command-line arguments due to: Unrecognized option: -scheme > > usage: bin/solr config [-a <ACTION>] -c <NAME> -p <PROP> [-url <HOST>] [-v > <VALUE>] [-z <HOST>] > > List of options: > -a,--action <ACTION> Config API action, one of: set-property, > unset-property, set-user-property, > unset-user-property; default is 'set-property'. > -c,--name <NAME> Name of the collection. > -p,--property <PROP> Name of the Config API property to apply the > action to, such as: > 'updateHandler.autoSoftCommit.maxTime'. > -url,--solr-url <HOST> Base Solr URL, which can be used to determine > the zk-host if that's not known; defaults to: > http://localhost:8983<http://localhost:8983/>. > -v,--value <VALUE> Set the property to this value; accepts JSON > objects and strings. > -z,--zk-host <HOST> Zookeeper connection string; unnecessary if > ZK_HOST is defined in solr.in.sh; otherwise, > defaults to localhost:9983. > > Please see the Reference Guide for more tools documentation: > > https://solr.apache.org/guide/solr/latest/deployment-guide/solr-control-script-reference.html > > Huh? I did not pass an option "-scheme", so what is the error message > about? Even if this line was an erronous error message, I do not see where > I did anything wrong. > > I have also tried many variations of the CLI parameters (like also exactly > obeying the "usage" line), but all of them lead to the same error message. > > What am I missing? > Kind regards. > > >
