[
https://issues.apache.org/jira/browse/SOLR-7871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16252542#comment-16252542
]
Shawn Heisey commented on SOLR-7871:
------------------------------------
bq. The name of the file is .conf, but it's actually prop-file syntax that's
used.
Interesting. Being pedantic for a moment: I understand the desire to make
things easy for novice users and give them a config file they can recognize
easily ... but when the user is a veteran of Java-based software, they're going
to be a little bit irritated if they ever learn that the file is handled as
java properties and doesn't have a .properties extension. It would bug me.
Side note: Due to the proliferation of configuration formats that I already
mentioned, I do think we need a separate issue for a really major change:
Re-work how every aspect of the application is configured, in particular to
reduce the number of configuration formats. That's probably something to do in
master only, because a significant change like that would best be introduced
with a new major version.
bq. If you've got something else in mind, or can see a way to have even less
bash/batch logic though, I'm all for it.
I was indeed thinking about *general* improvements to SolrCLI, making the
actual script *extremely* simple. I don't think we can eliminate the script,
though if that were possible, it would be really cool.
One pretty major shift (that also needs its own issue) I would like to make
possible is the idea of Solr being two Java programs -- one program that serves
as a "control" process (with a very small max heap) that can start/stop/restart
the actual application (Jetty for now). Imagine a situation where you can edit
things like Solr's max heap in the UI and also restart Solr from the UI.
> 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,
> SOLR-7871.patch, SOLR-7871.patch, SOLR-7871.patch, SOLR-7871.patch,
> SOLR-7871.patch, SOLR-7871.patch, SOLR-7871.patch, 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]
