Re: external file field and fl parameter

2013-07-17 Thread Chris Hostetter
: Yes that worked, thanks Alan. The consistency of this api is challenging. It's important to understand what's happening here. fl, by default, only returns stored fields -- but you can also request psuedo-fields such as the results of functions, or the result of a Doc Transformer ...

Re: external file field and fl parameter

2013-07-17 Thread Chris Collins
Chris, the confusion from my perspective is the general inconsistency and natural growth of the API which is somewhat expected based upon its history. Obviously this isnt sql, there is no ansi body defining the query language. I understand well the difference between stored, indexed etc.

Re: external file field and fl parameter

2013-07-17 Thread Chris Hostetter
: reference to a few special values, such as id and score. Neither : of them are technically stored fields either, but afaik you dont need : to use field(id), field(score) for those. Can you honestly say that : is consistent? Nope. I wasn't defending the quirks of the API, or trying give

external file field and fl parameter

2013-07-14 Thread Chris Collins
I am playing with external file field for sorting. I created a dynamic field using the ExternalFileField type. I naively assumed that the fl argument would allow me to return the value the external field but doesnt seem to do so. For instance I have a defined a dynamic field: *_efloat

Re: external file field and fl parameter

2013-07-14 Thread Erick Erickson
Did you store the field? I.e. set stored=true? And does the EFF contain values for the docs you're returning? Best Erick On Sun, Jul 14, 2013 at 3:32 AM, Chris Collins ch...@geekychris.com wrote: I am playing with external file field for sorting. I created a dynamic field using the

Re: external file field and fl parameter

2013-07-14 Thread Chris Collins
Yep I did switch on stored=true in the field type. I was able to confirm a few ways that there are values for the eff by two methods: 1) changing desc to asc produced drastically different results. 2) debugging FileFloatSource the following was getting triggered filling the vals array:

Re: external file field and fl parameter

2013-07-14 Thread Shawn Heisey
On 7/14/2013 7:05 AM, Chris Collins wrote: Yep I did switch on stored=true in the field type. I was able to confirm a few ways that there are values for the eff by two methods: 1) changing desc to asc produced drastically different results. 2) debugging FileFloatSource the following was

Re: external file field and fl parameter

2013-07-14 Thread Chris Collins
Why would I be re-indexing an external file field? The whole purpose is that its brought in at runtime and not part of the index? C On Jul 14, 2013, at 10:13 AM, Shawn Heisey s...@elyograg.org wrote: On 7/14/2013 7:05 AM, Chris Collins wrote: Yep I did switch on stored=true in the field type.

Re: external file field and fl parameter

2013-07-14 Thread Alan Woodward
Hi Chris, Try wrapping the field name in a field() function in your fl parameter list, like so: fl=field(eff_field_name) Alan Woodward www.flax.co.uk On 14 Jul 2013, at 18:41, Chris Collins wrote: Why would I be re-indexing an external file field? The whole purpose is that its brought in

Re: external file field and fl parameter

2013-07-14 Thread Chris Collins
Yes that worked, thanks Alan. The consistency of this api is challenging. C On Jul 14, 2013, at 11:03 AM, Alan Woodward a...@flax.co.uk wrote: Hi Chris, Try wrapping the field name in a field() function in your fl parameter list, like so: fl=field(eff_field_name) Alan Woodward