>> Hi all, >> >> I was wondering why String is not allowed in the (javascript)expressions? Is >> there a fundamental thing 'wrong' with that? > Op 7 apr. 2014 om 15:49 heeft Erick Erickson <[email protected]> het > volgende geschreven: > > Hmmm, how about a little context here?
Fair enough. I'm experimenting with dynamic facets, ranges and filters. I, for example, really enjoyed the geo spatial range facets (<5km, <10km). It is a very useful feature. I found it very useful to add a value source that computes the difference between two numeric fields, as it gives an option to filter "where fieldA>fieldB", which in turn comes in handy for date-intervals. (End date minus start date). I know string addition and subtraction do not make much sense, but comparison does and being able to put strings into the expressions would allow a more generic approach. It would (maybe?) also allow dynamic string facets like (A-C, D-F, etc) without the need to hard code these ranges in the taxonomy. But I'm not too familiar with all the options and features that lucene offers for this. (I still need to check the sortedset doc values etc.) Sorting on strings is already implemented in the Sort that can be passed to a search() call, but I think that is currently handled differently. Just curious what the options are here, and why the limitation exists. > >> On Mon, Apr 7, 2014 at 2:54 AM, Rob Audenaerde <[email protected]> >> wrote: >> Hi all, >> >> I was wondering why String is not allowed in the (javascript)expressions? Is >> there a fundamental thing 'wrong' with that? >> >> >> -Rob > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
