You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jan Høydahl (JIRA)" <ji...@apache.org> on 2014/11/05 00:25:37 UTC
[jira] [Updated] (SOLR-6697) bin/solr start script should allow
setting SOLR_OPTS in solr.in.*
[ https://issues.apache.org/jira/browse/SOLR-6697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Høydahl updated SOLR-6697:
------------------------------
Summary: bin/solr start script should allow setting SOLR_OPTS in solr.in.* (was: bin/solr start script should allow setting ADDITIONAL_CMD_OPTS in solr.in.*)
> bin/solr start script should allow setting SOLR_OPTS in solr.in.*
> -----------------------------------------------------------------
>
> Key: SOLR-6697
> URL: https://issues.apache.org/jira/browse/SOLR-6697
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Affects Versions: 4.10.2
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Attachments: SOLR-6697.patch
>
>
> It is possible to set {{ADDITIONAL_CMD_OPTS}} in e.g. {{solr.in.sh}}, but it should be documented by comments.
> Also, if you have set this in solr.in.sh, and then start with {{-a "some params"}}, these will overwrite the ADDITIONAL_CMD_OPTS set in the solr.in file. More logical would be for them to be appended.
--
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