Thank you, that helped me a lot.
Sven Teichmann
__
Software for Intellectual Property GmbH
Gewerbering 14a
83607 Holzkirchen (Germany)
Phone: +49 (0)8024 46699-00
Fax:+49 (0)8024 46699-02
E-Mail: s.teichm...@s4ip.de
Local Court of Munich
On Tue, May 13, 2014 at 1:34 AM, Sven Teichmann wrote:
> 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
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
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 an
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 wro
Hi,
I would index it in a field, you can use the database id and even add
additional information so compose your own key and retrieve that (only)
when you collect search results.
Wouter
> Hi,
>
> what is the best way to retrieve our "real" ids (as they are in our
> database) while searching?
>
>