[
https://issues.apache.org/jira/browse/SOLR-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158293#comment-16158293
]
Jan Høydahl commented on SOLR-7871:
-----------------------------------
[~covolution], [~ichattopadhyaya], [~noble.paul]: Please chime in so we get a
good consensus before writing a lot of code :)
My thinking is that if the back-compat logic is 95% equal as today (with
exception of resolving solr.in.sh location in Java-land) but we still keep all
env.variable names as today, then we have a chance of deprecating the old
configs in 7.x and introduce the new format from 8.0.
Then, once we have the new solr.conf or solr.yml, we can start supporting
lowercase dot separated keys as an alternative, we can start renaming some keys
while keeping support for the old name as an alias etc.
> 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
> Attachments: SOLR-7871.patch, SOLR-7871.patch, 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
