lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-11843) Admin UI -- collection creation sends routerField parameter instead of router.field
Date Tue, 16 Jan 2018 20:36:00 GMT

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

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

Finally figured out the correct javascript syntax.  Attached a patch that seems to fix the
problem (and the extra parameter that Erick noticed).

> 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
>
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message