w.thetaphi.de
>> eMail: u...@thetaphi.de
>>
>>
>>> -Original Message-
>>> From: Christian Reuschling [mailto:christian.reuschl...@gmail.com]
>>> Sent: Monday, November 07, 2011 8:17 PM
>>> To: java-user@lucene.apache.org
>>> Subje
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: Christian Reuschling [mailto:christian.reuschl...@gmail.com]
Sent: Monday, November 07, 2011 8:17 PM
To: java-user@lucene.apache.org
Subject: Re: Numeric field min max values
hm -
> -Original Message-
> From: Christian Reuschling [mailto:christian.reuschl...@gmail.com]
> Sent: Monday, November 07, 2011 8:17 PM
> To: java-user@lucene.apache.org
> Subject: Re: Numeric field min max values
>
> hm - I recognized that when I iterate with TermEnum
hm - I recognized that when I iterate with TermEnum and decode the
value with prefixCodedToInt (..), I get correct values, but I also get
values that are not Field values of this field in the entire index.
E.g. I get in the number-encoded field with the timestams also a '0'
as term - but all docume
Thank you very much! This exactly solves my problem
2011/11/3 Ian Lea :
> I can't answer most of the questions, but oal.util.NumericUtils has
> prefixCodedToInt (Long, etc) methods that will convert the encoded
> value (what you are seeing, I presume) to int or long or whatever.
> Maybe that will
I can't answer most of the questions, but oal.util.NumericUtils has
prefixCodedToInt (Long, etc) methods that will convert the encoded
value (what you are seeing, I presume) to int or long or whatever.
Maybe that will help.
--
Ian.
On Wed, Nov 2, 2011 at 7:19 PM, Christian Reuschling
wrote:
>
Hi,
maybe it is an easy question - I searched over the lucene-user
archive, but sadly didn't found an answer :(
I currently change our field logic from string- to numeric fields.
Until now, I managed to find the min-max values of a field by
iterating over the field with a TermEnum
(termEnum = rea
