Hi,
I may be missing something obvious, but how do I get the payloads for
the specific token positions that were matched by a query?
For example, if I have a phrase query like "A keyword B" that matches
the field "A keyword B A", I can get the payloads for A and B with
IndexReader.termPositions()
>From the user perspective: a public constructor would be the most
obvious, and would be consistent with RAMDirectory.
Dmitri
On Wed, Nov 12, 2008 at 4:50 AM, Michael McCandless
<[EMAIL PROTECTED]> wrote:
>
> I think we really should open up a non-static way to choose a different
> FSDirectory im
Nice!
At 8 threads nio-shared catches up with ram-shared. Here's the complete table:
fs-thread nio-thread ram-thread fs-shared
nio-shared ram-shared
1 71877 70461 54739 73986 72155 61595
2 34949 34945 26735 43719 33019 28935
3
gt; Those two additions are our current hope for what your seeing...would be
> nice to know if we need to try for more (or if we need to petition the smart
> people that work on that stuff to try for more ;) ).
>
> - Mark
>
> Dmitri Bichko wrote:
>>
>> Hi,
>>
&g
-shared case should have been hurt by using a
> non-read-only IndexReader.
>
> Mike
>
> Dmitri Bichko wrote:
>
>> Hi,
>>
>> I'm pretty new to Lucene, so please bear with me if this has been
>> covered before.
>>
>> The wiki suggests sharing
Hi,
I'm pretty new to Lucene, so please bear with me if this has been
covered before.
The wiki suggests sharing a single IndexSearcher between threads for
best performance
(http://wiki.apache.org/lucene-java/ImproveSearchingSpeed). I've
tested running the same set of queries with: multiple threa
Hi,
I'm putting together a cheap indexing server for an "explorative" lucene
project and had a few questions about which route to go.
I am going with a Socket 939 platform - does it make sense to get the
dual core Athlon 64 X2, or is it better to stick with a faster clocked
"plain" Athlon 64?
Al
