[
https://issues.apache.org/jira/browse/SOLR-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14654285#comment-14654285
]
Jan Høydahl commented on SOLR-7871:
-----------------------------------
Questions that need to be solved
* Some of the properties such as JVM options need to be injected when Java
starts
* What config format to choose, where it should live and what to name the file
* Upgradability - as suggested before, perhaps Solr should ship with e.g.
{{bin/solr.yml.template}} and never overwrite user's copy
Benefits of {{.yml}} is that it is future proof, supporting lists and other
structures, but {{.properties}} is probably good enough for our needs.
> 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
> Labels: bin/solr
> Fix For: Trunk
>
>
> 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]
