lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <j...@apache.org>
Subject [jira] [Updated] (SOLR-6697) bin/solr start script should allow setting SOLR_OPTS in solr.in.*
Date Tue, 04 Nov 2014 23:32:33 GMT

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

Jan Høydahl updated SOLR-6697:
------------------------------
    Attachment: SOLR-6697.patch

Moved changes entry to "Other changes" section since this is not really a bug fix. Question
is if we should add features to solr/bin in 4.10.x releases at all like we did in 4.10.2.
I'd say yes for now...

> 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
>             Fix For: 4.10.3, 5.0, Trunk
>
>         Attachments: SOLR-6697.patch, 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


Mime
View raw message