[
https://issues.apache.org/jira/browse/SOLR-11843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333284#comment-16333284
]
Shawn Heisey commented on SOLR-11843:
-------------------------------------
I'm not taking any action on the idea of adjusting the API to camelCase. The
whole API probably needs a review and strict standardization, though that
likely needs to take place in the v2 API, not the current one.
> Admin UI -- collection creation sends routerField parameter instead of
> router.field
> -----------------------------------------------------------------------------------
>
> Key: SOLR-11843
> URL: https://issues.apache.org/jira/browse/SOLR-11843
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Admin UI
> Affects Versions: 6.0
> Reporter: Shawn Heisey
> Priority: Major
> Attachments: SOLR-11843.patch, SOLR-11843.patch
>
>
> One of the important fields for collection creation is the router.field
> parameter. This shows up in the admin UI as "routerField" and when you enter
> a value there, the admin UI sends this information in the collections API
> request as a parameter named routerField ... but it should be sent as
> "router.field" instead.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
