Ah, yes that's it.
But why is it not indexed with LongPoint?
At least I cannot see it while inspecting with luke-7.1.0.
And also get no query results for "modified:[0 TO *]".
With LegacyLongField everything looks and works fine.
Feels like LongPoint is a bad replace for LegacyLongField, isn't it?
Regards
Bernd
Am 25.10.2017 um 12:17 schrieb Alan Woodward:
> Hi Bernd,
>
> You add a separate StoredField with the same name.
>
>> On 25 Oct 2017, at 11:11, Bernd Fehling <bernd.fehl...@uni-bielefeld.de>
>> wrote:
>>
>> With Lucene 6.6.2 I'm trying to get a LongPoint value indexed and stored.
>>
>> Old code:
>> LegacyLongField dateField = new LegacyLongField("modified", lastModified,
>> Field.Store.YES);
>>
>> Because LegacyLongField is deprecated I tried LongPoint.
>>
>> New code:
>> LongPoint dateField = new LongPoint("modified", lastModified);
>>
>> But how to set Field.Store.YES ???
>>
>> Regards
>> Bernd
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
