[
https://issues.apache.org/jira/browse/SOLR-11176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christine Poerschke updated SOLR-11176:
---------------------------------------
Attachment: SOLR-11176.patch
Attaching patch that also includes equivalent {{bin/solr.cmd}} script change. I
have no real experience with Windows shell script but this seems to work though
it also seems rather long-winded and awkward.
So all-in unless there's a better simplier solr.cmd way I'm minded to abandon
the idea of differentiating between _SOLR_TIMEZONE is unset_ and _SOLR_TIMEZONE
is set to empty value_.
> support set-but-empty SOLR_TIMEZONE in bin/solr
> -----------------------------------------------
>
> Key: SOLR-11176
> URL: https://issues.apache.org/jira/browse/SOLR-11176
> Project: Solr
> Issue Type: Task
> Components: scripts and tools
> Reporter: Christine Poerschke
> Assignee: Christine Poerschke
> Priority: Minor
> Attachments: SOLR-11176.patch, SOLR-11176.patch
>
>
> Existing behaviour:
> * SOLR_TIMEZONE is unset: default to UTC
> * SOLR_TIMEZONE is set but empty: default to UTC
> * SOLR_TIMEZONE is set: use the set value
> Proposed alternative behaviour:
> * SOLR_TIMEZONE is unset: default to UTC
> * SOLR_TIMEZONE is set but empty: {{-Duser.timezone}} is _not_ added to the
> command line
> * SOLR_TIMEZONE is set: use the set value
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
