[
https://issues.apache.org/jira/browse/SOLR-11645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254162#comment-16254162
]
Erick Erickson commented on SOLR-11645:
---------------------------------------
That's a valid point, I can argue both ways I guess.
1> sorting them makes it more likely that I'll even _notice_ I have them in
twice
2> presenting them in the order they're defined will tell me what's actually
going on.
either way is wrong ;)
Like I said, I don't have a strong preference here, just sayin'....
> When there are duplicate java commandline arguments, the Solr UI dashboard
> doesn't show Args at all
> ---------------------------------------------------------------------------------------------------
>
> Key: SOLR-11645
> URL: https://issues.apache.org/jira/browse/SOLR-11645
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
> Affects Versions: 7.1
> Reporter: Shawn Heisey
> Priority: Minor
> Attachments: SOLR-11645.patch, SOLR-11645.patch
>
>
> A user couldn't get the "Args" to display in the admin UI.
> Ultimately it was determined that they had duplicate arguments on their
> commandline, and this was resulting in an error in the browser:
> {code}
> Error: [ngRepeat:dupes] Duplicates in a repeater are not allowed. Use
> 'track by' expression to specify unique keys. Repeater: arg in
> commandLineArgs, Duplicate key: string:-XX:+UseGCLogFileRotation, Duplicate
> value: -XX:+UseGCLogFileRotation
> {code}
--
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
