On Friday 05 December 2003 10:45, Doug Cutting wrote:
> Tatu Saloranta wrote:
> > Also, shouldn't there be at least 3 methods that take Readers; one for
> > Text-like handling, another for UnStored, and last for UnIndexed.
>
> How do you store the contents of a Reader? You'd have to double-buffer
Tatu Saloranta wrote:
Also, shouldn't there be at least 3 methods that take Readers; one for
Text-like handling, another for UnStored, and last for UnIndexed.
How do you store the contents of a Reader? You'd have to double-buffer
it, first reading it into a String to store, and then tokenizing t
On Friday 05 December 2003 08:22, Erik Hatcher wrote:
> On Friday, December 5, 2003, at 09:48 AM, Grant Ingersoll wrote:
...
> > Field.Text(String, String) instead of the Field.Text(String, Reader)
> > version, which means I am storing the contents in the index.
>
> So use Field.UnStored(String, S
On Friday, December 5, 2003, at 09:48 AM, Grant Ingersoll wrote:
I have seen the example SAX based XML processing in the Lucene sandbox
(thanks to the authors for contributing!) and have successfully
adapted this approach for my application. The one thing that does not
sit well with me is the
you are storing the same information both ways. the string gets analyzed and
discarded, just like with the Reader.
Herb...
-Original Message-
From: Grant Ingersoll [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2003 9:49 AM
To: [EMAIL PROTECTED]
Subject: Index and Field.Text
Hi
Hi,
I have seen the example SAX based XML processing in the Lucene sandbox (thanks to the
authors for contributing!) and have successfully adapted this approach for my
application. The one thing that does not sit well with me is the fact that I am using
the method Field.Text(String, String) in