On Nov 16, 2009, at 9:20 AM, Yonik Seeley wrote: > On Mon, Nov 16, 2009 at 8:23 AM, Grant Ingersoll <gsing...@apache.org> wrote: >> One of the other things I think we are going to need is a cache for >> functions that are used this way. For instance, in the geo case, it is >> likely that we would both filter and score by distance, > > Filtering (bounding box) should be a separate, more efficient > operation than calculating distance,
In some cases, potentially, but I think it is going to depend on the application. > so I don't think any sort of > generic cache is needed for geo. Agreed, no generic cache for geo. Was thinking about a generic cache for function calculations. Potentially, we could have the need: sort, filter, facet and boost by function. And that calculation is likely the same over and over within a given request. Of course, if we add the pseudo-fields, then that effectively acts as a cache for the request. -Grant
