lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SOLR-705) Distributed search should optionally return docID->shard map
Date Tue, 19 Aug 2008 13:13:44 GMT

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

Yonik Seeley commented on SOLR-705:
-----------------------------------

bq. What about putting the docid->shard mapping elsewhere in the response rather than actually
on the document?

I've never been sure what the right answer is here.  Putting it in a different place sometimes
seems cleaner, but sometimes seems like it just makes responses harder to read, and forces
users to do their own id based correlation.

I've also thought about a "meta" part to a document that contains other information specific
to the document besides stored fields.

> 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-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.


Mime
View raw message