fq, not fl.
fq is "filter query"
fl is the "field list", the stored fields to be returned to the user.
Best,
Erick
On Thu, May 28, 2015 at 9:03 AM, John Blythe <j...@curvolabs.com> wrote:
> I've set the field to be processed as such:
> <fieldType name="sizes" class="solr.TrieDoubleField" precisionStep="6" />
>
> and then have this in the fl box in Solr admin UI:
> *, score, {!frange l=sum(size1, product(size1, .10))}size1
>
> I'm trying to use the size1 field as the item upon which a frange is being
> used, but also need to use the size1 value for the mathematical functions
> themselves
>
> I get this error:
> error": { "msg": "Error parsing fieldname", "code": 400 }
>
> thanks for any assistance or insight
>
> --
> *John Blythe*
> Product Manager & Lead Developer
>
> 251.605.3071 | j...@curvolabs.com
> www.curvolabs.com
>
> 58 Adams Ave
> Evansville, IN 47713
>
> On Wed, May 27, 2015 at 2:10 PM, John Blythe <j...@curvolabs.com> wrote:
>
>> thanks erick. will give it a whirl later today and report back tonight or
>> tomorrow. i imagine i'll have some more questions crop up :)
>>
>> best,
>>
>> --
>> *John Blythe*
>> Product Manager & Lead Developer
>>
>> 251.605.3071 | j...@curvolabs.com
>> www.curvolabs.com
>>
>> 58 Adams Ave
>> Evansville, IN 47713
>>
>> On Wed, May 27, 2015 at 1:32 PM, Erick Erickson <erickerick...@gmail.com>
>> wrote:
>>
>>> 1> tfloat
>>> 2> fq=dimField:[4.5 TO 5.5] or even use frange to set the lower and
>>> upper bounds via function
>>>
>>> Best,
>>> Erick
>>>
>>> On Wed, May 27, 2015 at 5:29 AM, John Blythe <j...@curvolabs.com> wrote:
>>> > hi all,
>>> >
>>> > i'm attempting to suggest products across a range to users based on
>>> > dimensions. if there is a "5x10mm Drill Set" for instance and a
>>> competitor
>>> > sales something similar enough then i'd like to have it shown. the
>>> range,
>>> > however, would need to be dynamic. i'm thinking for our initial testing
>>> > phase we'll go with 10% in either direction of a number.
>>> >
>>> > thus, a document that hits "drill set" but has the size1 field set to
>>> 4.5
>>> > or 5.5 would match for the "5" in the query.
>>> >
>>> > 1) what's the best field type to use for numeric ranges? i'll need to
>>> > account for decimal places, up to two places though usually only one.
>>> > 2) is there a way to dynamically set the range?
>>> >
>>> > thanks!
>>>
>>
>>
