lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-7059) Using paramset with multi-valued keys leads to a 500
Date Thu, 29 Jan 2015 08:19:34 GMT

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

ASF subversion and git services commented on SOLR-7059:
-------------------------------------------------------

Commit 1655547 from [~noble.paul] in branch 'dev/branches/lucene_solr_5_0'
[ https://svn.apache.org/r1655547 ]

SOLR-7059: Using paramset with multi-valued keys leads to a 500. SolrParams need an aray instead
of a list

> Using paramset with multi-valued keys leads to a 500
> ----------------------------------------------------
>
>                 Key: SOLR-7059
>                 URL: https://issues.apache.org/jira/browse/SOLR-7059
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 5.0
>            Reporter: Anshum Gupta
>            Assignee: Noble Paul
>
> Here's my use case:
> I wanted to use param-sets to have {{facet.field=field1&facet.field=field2}}
> For the same, here is what I updated:
> {code}
> curl http://localhost:8983/solr/bike/config/params -H 'Content-type:application/json'
-d 
> '{
>   "update" : { 
>     "facets" : {
>       "facet.field":["start_station_name","end_station_name"]
>     }
>   }
> }'
> {code}
> When I tried to use the same, I got a 500.
> After looking at the code, seems like, RequestParams uses MapSolrParams, which banks
on Map<String,String> map.
> This would need to change to support the multi-values.
> I also tried sending:
> {code}
> solr-5.0.0-SNAPSHOT > curl http://localhost:8983/solr/bike/config/params -H 'Content-type:application/json'
-d '{"update" : { "facets" : {"facet.field":"start_station_name","facet.field":"end_station_name"}}}'
> {code}
> This overwrote the value of facet.field with the last seen/parsed value i.e. there was
only one value in the end. This is expected as that's noggit's behavior i.e.  doesn't complain
and just overwrites the previous value with the same key.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message