You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2016/10/18 14:39:58 UTC

[jira] [Updated] (SOLR-7850) Move user customization out of solr.in.* scripts

     [ https://issues.apache.org/jira/browse/SOLR-7850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Smiley updated SOLR-7850:
-------------------------------
    Attachment: SOLR_7850_move_bin_solr_in_sh_defaults_into_bin_solr.patch

Here's an updated patch that addresses the Windows side.  I also did a little tweaking to make the declaration order a little more consistent between the Bash & Windows scripts.  I did a little testing in Windows but I should do more.

[~janhoy] might you take a look please?

> Move user customization out of solr.in.* scripts
> ------------------------------------------------
>
>                 Key: SOLR-7850
>                 URL: https://issues.apache.org/jira/browse/SOLR-7850
>             Project: Solr
>          Issue Type: Improvement
>          Components: scripts and tools
>    Affects Versions: 5.2.1
>            Reporter: Shawn Heisey
>            Priority: Minor
>         Attachments: SOLR_7850_move_bin_solr_in_sh_defaults_into_bin_solr.patch, SOLR_7850_move_bin_solr_in_sh_defaults_into_bin_solr.patch
>
>
> I've seen a fair number of users customizing solr.in.* scripts to make changes to their Solr installs.  I think the documentation suggests this, though I haven't confirmed.
> One possible problem with this is that we might make changes in those scripts which such a user would want in their setup, but if they replace the script with the one in the new version, they will lose their customizations.
> I propose instead that we have the startup script look for and utilize a user customization script, in a similar manner to linux init scripts that look for /etc/default/packagename, but are able to function without it.  I'm not entirely sure where the script should live or what it should be called.  One idea is server/etc/userconfig.\{sh,cmd\} ... but I haven't put a lot of thought into it yet.
> If the internal behavior of our scripts is largely replaced by a small java app as detailed in SOLR-7043, then the same thing should apply there -- have a config file for a user to specify settings, but work perfectly if that config file is absent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org