[ 
https://issues.apache.org/jira/browse/SOLR-16970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771865#comment-17771865
 ] 

ASF subversion and git services commented on SOLR-16970:
--------------------------------------------------------

Commit bd6f7f4c802583eddaddd70bfb39e3898d3f0ff3 in solr's branch 
refs/heads/branch_9_4 from Houston Putman
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=bd6f7f4c802 ]

SOLR-16970: Fix windows script (#1975)

(cherry picked from commit 74ad7bb029778e66576470419a29c04d4b6ecf17)


> SOLR_OPTS is unable to override many sysProps
> ---------------------------------------------
>
>                 Key: SOLR-16970
>                 URL: https://issues.apache.org/jira/browse/SOLR-16970
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Houston Putman
>            Assignee: Houston Putman
>            Priority: Major
>             Fix For: 9.4
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> Because of the way that the system properties are put together to run Solr in 
> bin/solr, the options that are set by Solr, such as the SSL, Auth, etc, are 
> appended to the end of the SOLR_OPTS variable. That means that the options 
> provided by users cannot override the options set by Solr.
> I'm pretty sure this isn't our goal. Any option provided by Solr should be 
> overridable by the user, using SOLR_OPTS. So we should change the way that 
> bin/solr constructs the solr start options, so that this is the case.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to