[
https://issues.apache.org/jira/browse/SOLR-11108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16148383#comment-16148383
]
Jason Gerlowski commented on SOLR-11108:
----------------------------------------
I set in to work on this, but I'm having trouble using the ConfigTool as the
proposed new warning message suggests:
{code}
[~/c/l/solr] $ bin/solr config -h
ERROR: config is not a valid command!
Usage: solr COMMAND OPTIONS
where COMMAND is one of: start, stop, restart, status, healthcheck,
create, create_core, create_collection, delete, version, zk, auth, assert
Standalone server example (start Solr running in the background on port 8984):
./solr start -p 8984
SolrCloud example (start Solr running in SolrCloud mode using localhost:2181
to connect to Zookeeper, with 1g max heap size and remote Java debug options
enabled):
./solr start -c -m 1g -z localhost:2181 -a "-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044"
Pass -help after any COMMAND to see command-specific usage information,
such as: ./solr start -help or ./solr stop -help
{code}
Taking a peek at {{bin/solr}} it does look like there's no plumbing that would
allow {{bin/solr config}} to work. I assumed from Jan's comment above that
"bin/solr config" would work, but that it was missing support for a few
options. Maybe the implied first step is that ConfigTool needs exposed from
the control scripts in the first place.
> Shorten _default configset warning and use ConfigTool
> -----------------------------------------------------
>
> Key: SOLR-11108
> URL: https://issues.apache.org/jira/browse/SOLR-11108
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: scripts and tools
> Affects Versions: 7.0
> Reporter: Jan Høydahl
> Fix For: 7.1
>
>
> In SOLR-10920 a WARNING was added when creating a data driven collection with
> config-set _default.
> That output from {{bin/solr}} is quite heavy:
> {noformat}
> WARNING: Using _default configset. Data driven schema functionality is
> enabled by default, which is
> NOT RECOMMENDED for production use.
> To turn it off:
> curl http://localhost:8983/solr/foo/config -d
> '{"set-user-property": {"update.autoCreateFields":"false"}}'
> {noformat}
> Suggest this output instead, avoiding cURL:
> {noformat}
> WARNING: Using _default configset with data driven schema functionality. NOT
> RECOMMENDED for production use.
> To turn off: bin/solr config -c mycoll -p myport -property
> update.autoCreateFields -value false
> {noformat}
> We already have the {{ConfigTool}} in SolrCLI, but it needs to understand
> {{-c}} in addition to {{-collection}} and {{-p}} in addition to {{-solrUrl}}
> to be more familiar.
> Also suggest to move the printout from bin/solr and bin/solr.cmd to SolrCLI
> at the same time.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
