[ https://issues.apache.org/jira/browse/SOLR-705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737018#action_12737018 ]
Hoss Man commented on SOLR-705: ------------------------------- i wasn't suggesting that the binary format couldn't handle it ... i was just suggesting that *if* the client fails to specify a "meta" fieldname for the response writer to use when including the metadata in each doc, the behavior can be implementation (ie: response writer) dependent. i'm speaking to what the "spec" for metadata fields *could* look like, not what the implementations *should* look like. > Distributed search should optionally return docID->shard map > ------------------------------------------------------------ > > Key: SOLR-705 > URL: https://issues.apache.org/jira/browse/SOLR-705 > Project: Solr > Issue Type: Improvement > Affects Versions: 1.3 > Environment: all > Reporter: Brian Whitman > Fix For: 1.4 > > Attachments: SOLR-705.patch, SOLR-705.patch, SOLR-705.patch, > SOLR-705.patch, SOLR-705.patch, SOLR-705.patch > > > SOLR-303 queries with &shards parameters set need to return the dociD->shard > mapping in the response. Without it, updating/deleting documents when the # > of shards is variable is hard. We currently set this with a special > requestHandler that filters /update and inserts the shard as a field in the > index but it would be better if the shard location came back in the query > response outside of the index. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.