Hello, > > - Remove the empty field (see mailing list Lucene dev 4/16/2003 message from > > Otis) > > Well... I thought it was just reported as a bug. I don't see any > responses to this, so I guess this is still a bug, and Luke is not the > one to be fixed. :-)
Sure - I meant HIDE this field in the summary as a temporary solution but it would be better to solve the problem in Lucene of course. > > - Information about the # of segments > > Need to check this, but shouldn't be any problem. I'm not sure whether > it's useful, though... ? It 's an indication of whether or not an index has to be optimized. ----- Original Message ----- From: "Andrzej Bialecki" <[EMAIL PROTECTED]> To: "Lucene Users List" <[EMAIL PROTECTED]> Sent: Monday, August 11, 2003 7:55 PM Subject: Re: Luke v 0.2 - Lucene Index Browser > Julien Nioche wrote: > > > Hello, > > > > Thanks to Andrzej for this new version! Luke is really useful. > > > > You're welcome. It was fun to code. > > > > >>open the original Dokuments with the platform dependant mimetype viewer > > Someone else already explained the problems with this... What is a > document in Lucene? It's a set of fields and their String values (or > their terms), so it's not possible to open the original document from > which the values were extracted, because there is no original... > > > > > ??? > > > > My suggestions by order of importance would be : > > > > - History of the 5 last indexes used : under the File Menu item ? > > No problem. I mean, technically it's no problem, it's just a problem of > getting to it on my so called "free time" ... > > > - Remove the empty field (see mailing list Lucene dev 4/16/2003 message from > > Otis) > > Well... I thought it was just reported as a bug. I don't see any > responses to this, so I guess this is still a bug, and Luke is not the > one to be fixed. :-) > > > - Possibility to merge different indexes > > No problem. > > > - Information about the # of segments > > Need to check this, but shouldn't be any problem. I'm not sure whether > it's useful, though... ? > > > [- and almost impossible : recompose the unstored fields of a document] > > It's not impossible, just time-consuming - all information (except the > parts removed by analyzer) is already there. This functionality has a > high "cool-ness" factor, which makes it very tempting... :-) > > Thanks for these suggestions! I can't promise any timeline, but > eventually I'd like to include this functionality in Luke. Patches are > always welcome... :-) > > -- > Best regards, > Andrzej Bialecki > > ------------------------------------------------- > Software Architect, System Integration Specialist > CEN/ISSS EC Workshop, ECIMF project chair > EU FP6 E-Commerce Expert/Evaluator > ------------------------------------------------- > FreeBSD developer (http://www.freebsd.org) > > > > > --------------------------------------------------------------------- > 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]
