OK, thx guys. I see the different options more clear now. 2009/7/4 Uwe Schindler <u...@thetaphi.de>
> Then see my other mail about Java Serialization. It works (but not so > fast), > but is the simpliest way to do it. > > I do not use the serialized fields during searching, I store them only for > usage in some special maintenance tasks on the indexed documents. So it's > the same use-case. > > For this use case serialization speed is enough. > > ----- > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > > -----Original Message----- > > From: MilleBii [mailto:mille...@gmail.com] > > Sent: Saturday, July 04, 2009 10:26 AM > > To: java-user@lucene.apache.org > > Subject: Re: Storing a serialized object ? > > > > Right I'm not indexing such fields, they are actually a kind of document > > property of my own > > > > 2009/7/4 Uwe Schindler <u...@thetaphi.de> > > > > > > That is one way, or you do it base64 encoded in a text field if don't > > > > care about space at all. :) > > > > > > Lucene also have binary fields for storing. Searching on such fields > > does > > > not make sense, so its ok to not be able to index them (how should that > > > work). > > > > > > I have this use case, too. Sometimes it is senseful to store arbitrary > > > objects as stored fields in the index and use then e.g. when displaying > > > search results. > > > > > > Uwe > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > > > For additional commands, e-mail: java-user-h...@lucene.apache.org > > > > > > > > > > > > -- > > -MilleBii- > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > -- -MilleBii-
