Thanks for the explanation, I'm not in this situation but it's helpful to
understand better lucene.
Nicola
Michael McCandless wrote:
>On Tue, May 14, 2013 at 10:02 AM, Nicola Buso wrote:
>
>> I now this can sound horrible/flexible/... but this mean I can add two
>> documents with the same fie
On Tue, May 14, 2013 at 10:02 AM, Nicola Buso wrote:
> I now this can sound horrible/flexible/... but this mean I can add two
> documents with the same field name, but different configurations, for
> example different IndexOptions?
Yes and no :)
Lucene will happily index such drastically differ
I now this can sound horrible/flexible/... but this mean I can add two
documents with the same field name, but different configurations, for
example different IndexOptions?
Nicola.
On Tue, 2013-05-14 at 12:52 +0100, Nicola Buso wrote:
> OK, thanks for the reply!
>
>
> Nicola.
>
> On Tue, 2013
OK, thanks for the reply!
Nicola.
On Tue, 2013-05-14 at 14:19 +0300, Shai Erera wrote:
> If your documents always contain the same fields then yes. But in
> general, you can do:
>
>
> addDocument("f:value");
> commit();
>
> addDocument("c:value");
> commit();
>
> And each AtomicReader will c
If your documents *always* contain the same fields then yes. But in
general, you can do:
addDocument("f:value");
commit();
addDocument("c:value");
commit();
And each AtomicReader will contain different fields. As getFieldInfos()
documents "Get the {@link FieldInfos} describing all fields in *this
