On Tue, Jul 19, 2011 at 3:20 PM, Chris Hostetter
<hossman_luc...@fucit.org> 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
> : > search it's quite possible it would speed things up.
> :
> : 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
>
> isn't that kind of orthoginal to the question though? ... a user can use
> the new psuedo-field functionality to request values from the FieldCache
> instead of stored fields, but specificly in the case of distributed
> search, when the first request is only asking for the uniqueKey values and
> scores, shouldn't that use the FieldCache to get those values? (w/o the
> user needing to jumpt thorugh hoops in how the request is made/configured)
Well, I was pointing out that distributed search could be easily
modified to use the field-cache
by changing id to id:{!func}id
But I'm not sure we should do that by default - the memory of a full
fieldCache entry is non-trivial for some people.
Using a CSF id field would be better I think (the type were it doesn't
populate a fieldcache entry).
-Yonik
http://www.lucidimagination.com
