[
https://issues.apache.org/jira/browse/SOLR-17111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18017905#comment-18017905
]
Eric Pugh commented on SOLR-17111:
----------------------------------
A quick update that we've migrated quite a few properties, but there are many
more to go. The cwiki page now has a column that tells you the status of the
migrations. I AM going to have to take a pause on this effort howerver, which
means it may not get to "done done" before Solr 10 is cut. I've got four
conference talks + a workshop in the next two weeks, and I need to focus on
them.
Fortunately, the backwards compatible aspect appears to work well, so we can
migrate system properties during the lifecycle of Solr 10.
I do plan on landing [https://github.com/apache/solr/pull/3608] to move us the
pattern for mapping properties that will work throughout Solr 10 and Solr 11.
Likewise, I'd like to get the bootstrap parameters to done since we've put a
lot of work into them: https://github.com/apache/solr/pull/3604/.
> SIP-21: Standardize system property naming
> ------------------------------------------
>
> Key: SOLR-17111
> URL: https://issues.apache.org/jira/browse/SOLR-17111
> Project: Solr
> Issue Type: Improvement
> Reporter: Jan Høydahl
> Priority: Major
>
> [SIP-21 Standardize system property
> naming|https://cwiki.apache.org/confluence/display/SOLR/SIP-21%3A+Standardize+system+property+naming]
> ([dev-list
> thread|https://lists.apache.org/thread/ckb3tqnjf0h66rd0mlpfblpvkrvp3wq6])
> Followup from SOLR-15960.
> This Jira will standardize naming of system properties in use by Solr with
> rules
> * Lowercase {{[a-z0-9\.]}} only
> * All props start with {{solr.}}
> * All props === env.var (when uppercased and {{{}.replace("-","_"){}}})
> See
> [EnvToSyspropMappings.properties|https://github.com/apache/solr/blob/main/solr/core/src/resources/EnvToSyspropMappings.properties]
> for a list of identified non-standard system property names. It may not be
> complete. And some are impossible to change, such as
> {{{}SOLR_PORT=jetty.port{}}}.
> I think it makes sense to add one child-task for each of the vars we want to
> standardize, so we can target one variable/property at a time. The process
> will be (using {{enable.packages}} as example:
> # Make our code and docs use "solr.enable.packages" everywhere
> # Make sure the old sysprop still works in 9.x (This may be automated using
> the properties file above)
> # Make a note in 9.x upgrade notes that "-Denable.packages" is deprecated
> # Add a section to 10.0 major changes that "-Denable.packages" no longer
> works from 10.0
> # Add a test? Perhaps it is enough to test the EnvUtils logic, i.e. that no
> matter which way you set the env/property our code
> {{EnvUtils.getProp("solr.enable.packages")}} gets hold of it?
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
