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

Shawn Heisey commented on SOLR-16466:
-------------------------------------

{quote}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?
{quote}
If I had my way they would never be sorted.  I want to see EXACTLY what Java 
actually got when I look at the arguments, and that data is lost if the list is 
sorted.  There might be differences in behavior when Java receives certain 
arguments in a different order, not even counting the same option being sent 
more than once.  I get why someone would want them sorted, which was why I 
suggested the UI option to sort them.  Maybe instead of an option, it could be 
a button that opens another page or a dialog box with the sorted list.

 

> 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: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to