[
https://issues.apache.org/jira/browse/SOLR-16466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17685931#comment-17685931
]
Jason Gerlowski commented on SOLR-16466:
----------------------------------------
bq. Sorting them, while it does make it easier to see if a particular option is
in use, loses the ability to figure out which option is actually taking effect
when it is being set to two different values
So, if I'm understanding the rationale here correctly, the goal of not sorting
is to make it clear which system property "wins" in a case where a custom
solr.in.sh file accidentally sets a given sysprop multiple times?
If that's the problem to solve, is making the sort optional the best fix?
Presumably we'd be making folks' lives even easier if the JS code itself
checked for sysprop names that appear twice, and put some red text right above
the argument list mentioning which arguments were specified multiple times and
which value "won" that collision. Or, alternatively if we find it easier to
avoid JS changes: if Solr logged a warning on startup about potential
misconfiguration.
> Admin UI - Make it optional to sort list of commandline args
> ------------------------------------------------------------
>
> Key: SOLR-16466
> URL: https://issues.apache.org/jira/browse/SOLR-16466
> Project: Solr
> Issue Type: Improvement
> Components: Admin UI
> Affects Versions: 9.0
> Reporter: Shawn Heisey
> Priority: Minor
> Labels: newdev
> Attachments: image-2022-10-18-17-55-33-446.png,
> image-2022-10-18-17-56-36-230.png
>
>
> It is sometimes detrimental to have the list of commandline arguments sorted
> in the Admin UI dashboard. One of the things I do whenever I install or
> upgrade Solr is to go into the javascript and remove the sort. I would like
> to make it optional on the dashboard to sort the arguments.
> I do not know how to go about doing this. My HTML/CSS/Javascript skills are
> not adequate to accomplish it. It's easy enough to remove ".sort()" from the
> javascript to turn it off, but making it optional (unchecking a checkbox and
> having that trigger some javascript) is something I would struggle to
> implement.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
