OK let's do it then... Yonik do you want to open issue, patch, etc.? We should spell this out clearly in the javadocs that this case (tokenStream + string/binary value) is handled "specially", because this does break from Field's "normal" semantics.
Mike On Tue, Jun 16, 2009 at 6:18 AM, Uwe Schindler<u...@thetaphi.de> wrote: > Yes, I exactly need this for NumericField! The numeric value gets indexed > using the tokenStream, but an optional stored field value (e.g. the number > as plain text or even prefixEncoded) would also be good. Currently the user > must index both types separate (but can use the same field name). As far as > I see, this is not a problem with the current indexer. The indexer first > tries tokenStreamValue() during indexing, but when saving the stored fields, > always stringValue()/getBinaryValue() is used. > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > >> -----Original Message----- >> From: Michael McCandless [mailto:luc...@mikemccandless.com] >> Sent: Tuesday, June 16, 2009 12:13 PM >> To: java-dev@lucene.apache.org; yo...@lucidimagination.com >> Subject: Re: Field.tokenStreamValue >> >> Seems reasonable? >> >> So you're saying that if a Field has both TokenStream and some other >> value, the TokenStream gets indexed into postings & term vectors, but >> the other value gets stored? >> >> Mike >> >> On Mon, Jun 15, 2009 at 9:48 PM, Yonik Seeley<yo...@lucidimagination.com> >> wrote: >> > The JavaDoc suggests that one can't have a tokenStreamValue and a >> > StringValue or binaryValue at the same time... any good reason for >> > this restriction? >> > >> > /** The value of the field as a String, or null. If null, the Reader >> value, >> > * binary value, or TokenStream value is used. Exactly one of >> stringValue(), >> > * readerValue(), getBinaryValue(), and tokenStreamValue() must be set. >> */ >> > >> > The indexing code looks like it should actually work - but the Field >> > restricts one setting a tokenStreamValue and having a stored field at >> > the same time. >> > Should we fix this? >> > >> > -Yonik >> > http://www.lucidimagination.com >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >> > For additional commands, e-mail: java-dev-h...@lucene.apache.org >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: java-dev-h...@lucene.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org
