On Fri, Apr 5, 2013 at 4:05 AM, Wei Wang welshw...@gmail.com wrote:
Do we need to use setLongValue() all the time?
Yes.
--
Adrien
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands,
A few quick questions about DocValues:
1. If only small number of documents have a ShortDocValueField defined,
should each document in the index has this field filled with some value?
The add() function of Document seems not enforce a DocValues field is
always added to each document.
2. Is there
Hi,
On Thu, Apr 4, 2013 at 10:30 AM, Wei Wang welshw...@gmail.com wrote:
A few quick questions about DocValues:
1. If only small number of documents have a ShortDocValueField defined,
should each document in the index has this field filled with some value?
The add() function of Document
Hi Adrien,
Thanks for the clarification. It is very helpful. Will try Lucene 4.2 and
AtomicReader API.
Wei
On Thu, Apr 4, 2013 at 11:22 AM, Adrien Grand jpou...@gmail.com wrote:
Hi,
On Thu, Apr 4, 2013 at 10:30 AM, Wei Wang welshw...@gmail.com wrote:
A few quick questions about DocValues:
Given the new Lucene 4.2 DocValues API, it seems no matter it is byte,
short, int, or long, they are all stored as NumericDocValuesField. Does
this mean long values are always stored regardless of the initial type?
If so, do we still save space if the value range is small? Do we need to
give some
On Thu, Apr 4, 2013 at 11:03 PM, Wei Wang welshw...@gmail.com wrote:
Given the new Lucene 4.2 DocValues API, it seems no matter it is byte,
short, int, or long, they are all stored as NumericDocValuesField. Does
this mean long values are always stored regardless of the initial type?
If so, do
We now start using NumericDocValuesField. The Javadoc says the old types
such as ShortDocValuesField is deprecated. So even the values of a field is
short, we still use NumericDocValuesField as the Javadoc suggests.
However, when we call function SetIntValue() of NumericDocValuesField, we
got an
