://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Christian Reuschling [mailto:christian.reuschl...@gmail.com]
> Sent: Wednesday, February 15, 2012 2:56 PM
> To: java-user@lucene.apache.org
> Subject: Re: Empty numeric field
>
> Uwe, thank you very much.
Uwe, thank you very much. This sounds like the pretty best solution!
2012/2/15 Uwe Schindler :
> Hi,
>
> Thanks for explanation. I almost expected that it has to do with" stored
> fields". It's easy to fix:
>
>> ah ok, I know what you mean. We have to read out the stored field values
>> later.
Hi,
Thanks for explanation. I almost expected that it has to do with" stored
fields". It's easy to fix:
> ah ok, I know what you mean. We have to read out the stored field values
> later.
> A field can have multiple (stored) values (several
> document.add(fieldable) invocations for one field).
ah ok, I know what you mean. We have to read out the stored field
values later. A field can have multiple (stored) values (several
document.add(fieldable) invocations for one field). Further, we have
the problem that some field values are logically related to each
other. Since Lucene has no possibi
Hi,
This looks like an XY problem
(http://www.perlmonks.org/index.pl?node_id=542341). Maybe you should first
explain to us, why you need that. In Lucene fields have no "equal length" or
something like that, especially numeric fields are tokenized and contain of
several tokens separately indexe
