Ok. I reverted back to the version without a public clear() method.
Wolfgang.
On Nov 27, 2006, at 12:17 PM, jm wrote:
yes that would be ok for my, as long as I can reuse my child analyzer.
On 11/27/06, Wolfgang Hoschek <[EMAIL PROTECTED]> wrote:
On Nov 27, 2006, at 9:57 AM, jm wrote:
On Nov 27, 2006, at 9:57 AM, jm wrote:
On 11/27/06, Wolfgang Hoschek <[EMAIL PROTECTED]> wrote:
On Nov 26, 2006, at 8:57 AM, jm wrote:
> I tested this. I use a single static analyzer for all my documents,
> and the caching analyzer was not working properly. I had to add a
>
und a data problem in
my tests, but as I was not going to pursue that improvement for now I
did not look into it.
Ok.
Wolfgang.
thanks,
javier
On 11/23/06, Wolfgang Hoschek <[EMAIL PROTECTED]> wrote:
Out of interest, I've checked an implementation of something like
this into Analyz
ying child analyzer
* @return a new analyzer
*/
public static Analyzer getTokenCachingAnalyzer(final Analyzer
child) { ... }
Check it out, and let me know if this is close to what you had in mind.
Wolfgang.
On Nov 22, 2006, at 9:19 AM, Wolfgang Hoschek wrote:
I've never tried it,
so it does not seem to
be an easy way to do that no?
thanks
On 11/21/06, Wolfgang Hoschek <[EMAIL PROTECTED]> wrote:
On Nov 21, 2006, at 12:38 PM, jm wrote:
> Ok, thanks, I'll give MemoryIndex a go, and if that is not good
enoguh
> I will explore the other options then.
On Nov 21, 2006, at 7:43 AM, jm wrote:
Hi,
I have to decide between using a RAMDirectory and MemoryIndex, but
not sure what approach will work better...
I have to run many items (tens of thousands) against some queries (100
at most), but I have to do it one item at a time. And I already have
e (iter.hasMoreElements()) {
Field field = (Field) iter.nextElement();
index.addField(field.name(), field.stringValue(), analyzer);
}
return index;
}
On 11/21/06, Wolfgang Hoschek <[EMAIL PROTECTED]> wrote:
On Nov 21, 2006, at 7:43 AM, jm wrote:
> Hi,
>
Document.get(FIELD_NAME) will always be null because MemoryIndex does
not store the original untokenized fulltext(s). Those full texts are
thrown away immediately after tokenization (i.e. on addField()),
keeping only the field names and associated (indexed) tokenized
terms. The latter a
Hi,
I am playing with MemoryIndex for a situation in which I have a large
number of small, ephemeral documents that I need to fire queries
at. It
appears to be at least 5x faster than RAMDirectory for my usage, which
is large enough to be interesting.
However MemoryIndex does not seem to sup
