[
https://issues.apache.org/jira/browse/SOLR-1557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12777321#action_12777321
]
Hoss Man commented on SOLR-1557:
--------------------------------
bq. I'm not sure I see the need or the benefit for "shard" to be multivalued
though.
the simplified specification of defaults in solrconfig.xml seems like reason
enough.
but it also seems like the "defaults" vs "appends" distinction of multivalued
params makes as much sense for shards as it does does for fq, etc... ie: i
want this shard to always be appended to the shards list because it's the
"current" shard, but let the client specify additional shards if they want to
also query older/alternate content in addition.
> shards param not parsed as a multivalue param
> ---------------------------------------------
>
> Key: SOLR-1557
> URL: https://issues.apache.org/jira/browse/SOLR-1557
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.4
> Reporter: Hoss Man
> Fix For: 1.5
>
>
> the shards param currently uses some odd parsing code to split on "," ... it
> should both allow whitespace, and allow the shards to be specified as a
> multi-valued param...
> http://old.nabble.com/Shards-param-accepts-spaces-between-commas--to25962879.html#a25962879
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
