[
https://issues.apache.org/jira/browse/SOLR-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357509#comment-15357509
]
Jan Høydahl commented on SOLR-7871:
-----------------------------------
I have continued a bit on this one.
My plan is to move the following functionality from {{solr.sh|cmd}} into a new
{{SolrCliConfig.java}}:
* Locate correct config file and location
* Parse the config file
* Resolve SOLR_PID_DIR, SOLR_TIP, DEFAULT_SERVER_DIR etc
* Configure defaults for SOLR_URL_SCHEME, SOLR_SSL_OPTS, SOLR_JETTY_CONFIG etc
The shell script will then call SolrCliConfig and get all variables in return.
In the first phase, we'll just return a string which the script can evaluate to
set all variables.
I propose that the new config file will be of a simple "properties" format
similar to {{solr.in.sh}} and be called {{solr.conf}}. The new SolrCliConfig
will use {{solr.conf}} if found, else fallback to and parse solr.in.\* as well,
for a smooth transition.
> Platform independent config file instead of solr.in.sh and solr.in.cmd
> ----------------------------------------------------------------------
>
> Key: SOLR-7871
> URL: https://issues.apache.org/jira/browse/SOLR-7871
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Affects Versions: 5.2.1
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Labels: bin/solr
> Fix For: 6.0
>
>
> Spinoff from SOLR-7043
> The config files {{solr.in.sh}} and {{solr.in.cmd}} are currently executable
> batch files, but all they do is to set environment variables for the start
> scripts on the format {{key=value}}
> Suggest to instead have one central platform independent config file e.g.
> {{bin/solr.yml}} or {{bin/solrstart.properties}} which is parsed by
> {{SolrCLI.java}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
