[jira] [Commented] (SOLR-11843) Admin UI -- collection creation sends routerField parameter instead of router.field

["Shawn Heisey (JIRA)" <ji...@apache.org>]

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

Shawn Heisey commented on SOLR-11843:
-------------------------------------

I'm reasonably certain that this has been a problem since 6.0, when the collections capability became available in the new admin UI.  I discovered the problem on 7.2.

I have no idea how to modify the javascript to fix the problem.  I tried a couple of ideas, but the first one completely broke the admin UI and the second one didn't work.


> 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
>
> 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
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org