Hi,
I also found this response very useful and right now I am playing around
with DocValues.
If the default DocValuesFormat isn't fast enough, you can always
switch to e.g. DirectDocValuesFormat (uses lots of RAM but it just an
array lookup).
How do I switch do DirectDocValuesFormat? And how do I receive the
DocValues then?
Sven
Am 07.05.2014 16:09, schrieb Wouter Heijke:
Hey Mike,
That was a very useful response, also for long time Lucene users like
myself who were stuck in legacy ways of doing things!
I managed to easily change indexing of keys to DocValues and found myself
wondering why I did not get anything returned, it appears indexing works
transparent to any field, but to get your DocValue key out of the 'index'
you need to use the AtomicReader... all now works like it did before, only
faster (i hope ;-))
Wouter
Doc values is far faster than a stored field.
If the default DocValuesFormat isn't fast enough, you can always
switch to e.g. DirectDocValuesFormat (uses lots of RAM but it just an
array lookup).
Mike McCandless
http://blog.mikemccandless.com
On Tue, May 6, 2014 at 4:33 AM, Sven Teichmann <s.teichm...@s4ip.de>
wrote:
Hi,
what is the best way to retrieve our "real" ids (as they are in our
database) while searching?
Right now we generate a file after indexing which contains all Lucene
docids
and the matching id in our database. Our own Collector converts the
docids
to our ids while collecting. This works as long as no document is
deleted
and the index optimized after it.
Is this a good solution or should we use Fields or DocValues for this?
What
is the fastest solution?
Regards,
Sven Teichmann
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-user-h...@lucene.apache.org
