Correct. No, there is no point in putting an empty field there. Otis
--- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi Otis > > What kind of implications does that produce on the search? > > If I understand correctly that record would not be searched for if > the > field is not there, correct? > But then is there a point putting an empty value in it, if an > application will never search for empty values? > > > thanks > > -pedja > > > Otis Gospodnetic said the following on 12/8/2004 1:31 AM: > > >Empty fields won't add any value, you can skip them. Documents in > an > >index don't have to be uniform. Each Document could have a > different > >set of fields. Of course, that has some obvious implications for > >search, but is perfectly fine technically. > > > >Otis > > > >--- "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > > > > > >>Here's probably a silly question, very newbish, but I had to ask. > >>Since I have mysql documents that contain over 30 fields each and > >>most of them > >>are added to the index, is it a common practice to add fields to > the > >>index with > >>empty values, for that perticular record, or should the field be > >>totally omitted. > >> > >>What I mean is if let's say a Title field is empty on a specific > >>record (in mysql) > >>should I still add that field into Lucene index with an empty value > >>or just > >>skip it and only add the fields that contain non-empty values? > >> > >>thanks > >> > >>-pedja > >> > >> > >> > >> > >>--------------------------------------------------------------------- > >>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] > > > > > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
