[
https://issues.apache.org/jira/browse/SOLR-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000684#comment-16000684
]
Ishan Chattopadhyaya edited comment on SOLR-7871 at 5/8/17 12:56 PM:
---------------------------------------------------------------------
+1 to doing this in 7.0 (and removing solr.in.sh/solr.in.cmd), and not
bothering about backcompat for solr.in.sh/solr.in.cmd.
I wonder, though, how will users retain their configurations when they upgrade
from 7.x to 7.y, esp. when 7.y introduces newer config defaults? Zookeeper has
the concept of zoo_sample.cfg that users then copy over to zoo.cfg. Is that
model worth consideration?
was (Author: ichattopadhyaya):
+1 to doing this in 7.0 (and removing solr.in.sh/solr.in.cmd), and not
bothering about backcompat for solr.in.sh/solr.in.cmd.
> 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: master (7.0)
>
> Attachments: SOLR-7871.patch
>
>
> 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.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
