Why not simply add the field twice, one time with TokenStream, one time stored only? Internally stored/indexed fields are handled like that.
----- Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: [email protected] > -----Original Message----- > From: Benjamin Heilbrunn [mailto:[email protected]] > Sent: Wednesday, January 13, 2010 2:31 PM > To: [email protected] > Subject: Re: Field creation with TokenStream and stored value > > Sorry for pushing this thing. > > Would it be possible to add the demanded constructor or would it break > anything of lucenes logic? > > > 2010/1/11 Benjamin Heilbrunn <[email protected]>: > > Hey out there, > > > > in lucene it's not possible to create a Field based on a TokenStream > > AND supply a stored value. > > > > Is there a reason why a Field constructor in the form of > > public Field(String name, TokenStream tokenStream, String > storedValue) > > does not exist? > > > > I am using trees of TeeSinkTokenFilter's for the creation of many > > fields, based on a source string. > > That's the reason why I can't use the "standardconstructor" > > public Field(String name, String value, Store store, Index index) > > > > > > Regards > > Benjamin > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
