t;
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Tue, Aug 16, 2016 at 6:00 AM, Rolf Veen wrote:
>
>> Hi, all.
>>
>> I had a piece of code to create a 'near' SoftField like this:
>>
>> public SortField distanceSortField(double x, d
Hi, all.
I had a piece of code to create a 'near' SoftField like this:
public SortField distanceSortField(double x, double y, IndexSearcher ix)
throws Exception {
Point pt = ctx.makePoint(x, y);
ValueSource valueSource = strategy.makeDistanceValueSource(pt,
DistanceUtils.DEG_TO_KM);
return
I've this scenario in a web application:
1. many users query a Lucene index concurrently (obvious)
2. one user can make several queries (she may have different browser
windows open)
3. all those queries need to have a consistent paging behavior (next,
previous buttons)
4. The index can be updated
StandardQueryParser.setNumericConfigMap().
This method has the drawback that the types must be known in advance
(that is, it is a schema), but it's more robust the guessing the types from
the documents itself (as my initial request implied).
Kind regards,
Rolf.
On Fri, Feb 1, 2013 at 3:22 PM, Rolf Veen
On Fri, Feb 1, 2013 at 12:43 PM, Michael McCandless
wrote:
> There is actually one way to check if a field was indexed numerically:
> you can seek to the first term in the field, and attempt to parse it
> as a long/float/etc., and if that throws a NumberFormatException, it
> was indexed numerical
On Thu, Jan 31, 2013 at 9:55 PM, Michael McCandless
wrote:
> But are you wanting to, eg, make a NumericRangeQuery if you detect the
> field was indexed numerically, and otherwise a TermRangeQuery, or
> something...? (Not easy)
This is what I want, yes. But I begin to understand that this is not
Field class was used for the
> indexing: that information is not fully preserved ...
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
> On Thu, Jan 31, 2013 at 6:33 AM, Rolf Veen wrote:
>> Hello, all.
>>
>> I want to get a list of field names and types out
