On Tue, Jul 19, 2011 at 3:20 PM, Chris Hostetter
wrote:
>
> : > Quite probably ... you typically can't assume that a FieldCache can be
> : > constructed for *any* field, but it should be a safe assumption for the
> : > uniqueKey field, so for that initial request of the mutiphase distributed
> : >
: > Quite probably ... you typically can't assume that a FieldCache can be
: > constructed for *any* field, but it should be a safe assumption for the
: > uniqueKey field, so for that initial request of the mutiphase distributed
: > search it's quite possible it would speed things up.
:
: Ah, tha
>
> Ah, thanks Hoss - I had meant to respond to the original email, but
> then I lost track of it.
>
> Via pseudo-fields, we actually already have the ability to retrieve
> values via FieldCache.
> fl=id:{!func}id
>
> But using CSF would probably be better here - no memory overhead for
> the FieldC
On Tue, Jul 5, 2011 at 5:13 PM, Chris Hostetter
wrote:
> : Correct me if I am wrong: In a standard distributed search with
> : QueryComponent, the first query sent to the shards asks for
> : fl=myUniqueKey or fl=myUniqueKey,score. When the response is being
> : generated to send back to the coor
: Correct me if I am wrong: In a standard distributed search with
: QueryComponent, the first query sent to the shards asks for
: fl=myUniqueKey or fl=myUniqueKey,score. When the response is being
: generated to send back to the coordinator, SolrIndexSearcher.doc (int i,
: Set fields) is cal
I am a user of Solr 3.2 and I make use of the distributed search capabilities
of Solr using a fairly simple architecture of a coordinator + some shards.
Correct me if I am wrong: In a standard distributed search with
QueryComponent, the first query sent to the shards asks for fl=myUniqueKey or
