On Nov 17, 2009, at 10:35 AM, Yonik Seeley wrote:
> On Mon, Nov 16, 2009 at 9:20 AM, Yonik Seeley
> wrote:
>> On Mon, Nov 16, 2009 at 8:23 AM, Grant Ingersoll 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
On Mon, Nov 16, 2009 at 9:20 AM, Yonik Seeley
wrote:
> On Mon, Nov 16, 2009 at 8:23 AM, Grant Ingersoll 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 an
On Nov 16, 2009, at 3:26 PM, Yonik Seeley wrote:
> On Mon, Nov 16, 2009 at 3:18 PM, Grant Ingersoll wrote:
>>> http://www.lucidimagination.com/blog/tag/frange/
>>
>> I notice in the implementation that it assumes float. What if I want double
>> range?
>
> That's the same generic problem as f
On Mon, Nov 16, 2009 at 3:18 PM, Grant Ingersoll wrote:
>> http://www.lucidimagination.com/blog/tag/frange/
>
> I notice in the implementation that it assumes float. What if I want double
> range?
That's the same generic problem as function query (float vs double vs
int vs long)... we haven't s
On Nov 15, 2009, at 5:07 PM, Yonik Seeley wrote:
> On Sat, Nov 14, 2009 at 2:30 PM, Grant Ingersoll wrote:
>> Is it at all meaningful to think about a function query acting as a Filter?
>> The basic idea being that if the score was above/below some value
>> (presumably 0 by default), then tha
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.
I think even more generally would be good -- an easy way to share
calculations between anything in the request cycle: functio
On Nov 16, 2009, at 9:20 AM, Yonik Seeley wrote:
> On Mon, Nov 16, 2009 at 8:23 AM, Grant Ingersoll 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 s
On Mon, Nov 16, 2009 at 8:23 AM, Grant Ingersoll 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
On Nov 15, 2009, at 8:32 PM, Grant Ingersoll wrote:
>
> On Nov 15, 2009, at 5:07 PM, Yonik Seeley wrote:
>
>> On Sat, Nov 14, 2009 at 2:30 PM, Grant Ingersoll wrote:
>>> Is it at all meaningful to think about a function query acting as a Filter?
>>> The basic idea being that if the score was
On Nov 15, 2009, at 5:07 PM, Yonik Seeley wrote:
> On Sat, Nov 14, 2009 at 2:30 PM, Grant Ingersoll wrote:
>> Is it at all meaningful to think about a function query acting as a Filter?
>> The basic idea being that if the score was above/below some value
>> (presumably 0 by default), then tha
On Sat, Nov 14, 2009 at 2:30 PM, Grant Ingersoll wrote:
> Is it at all meaningful to think about a function query acting as a Filter?
> The basic idea being that if the score was above/below some value (presumably
> 0 by default), then that particular document would be on/off.
frange?
http://
Is it at all meaningful to think about a function query acting as a Filter?
The basic idea being that if the score was above/below some value (presumably 0
by default), then that particular document would be on/off. Right now, Solr
can take in functions as fq params, but they don't really do a
12 matches
Mail list logo
