I keep hitting my thumb with the Rock. I guess that is better than severing my limb with the pneumatic hammer.
Congrats on the book Erik. Lucene seems really cool. I hope to work with it on a future project. My limbs seem to grow back. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 29, 2004 3:12 PM To: jug-discussion@tucson-jug.org Subject: Re: [jug-discussion] Searching large object graphs Not to be Trite... But why not just use bean objects to a backend DB. Or for that matter hand write the old incremental sort and sorted search routines. If it is all in memory then you should be able hand write an index system capable of running through thousands of records in a fraction of a second... Just seems easier... but then again I am not a CSE, so I don't get a lot of joy out of using the overly complex to do the overly simply just so I can learn about the overly complex for no more reason then I may need it latter. Or more simply, for me it is easier to hammer one loose nail with a near by rock then to set up a pneumatic nail gun. On Thu, 23 Dec 2004, Erik Hatcher wrote: > Lucene!!!! > > The query would be this "name:olson OR email:olson" if you indexed > that information into separate fields. A common technique is to index > all data you want queryable also into an aggregate field in which case > the query could simply be "olson". > > The full source code to Lucene in Action is at > http://www.manning.com/hatcher2 - the ebook is available. The > physical book is shipping from the printers as we speak (UPS tracking > says I should have gotten my batch yesterday, but it'll be today it seems). > http://www.lucenebook.com will go live within the week searching > *inside* the book as well as a blog system I'm setting up. > > Erik > > On Dec 22, 2004, at 10:27 PM, Tim Colson wrote: > > > So just assume for a moment that RAM is cheap and you decided to > > load 100K objects into memory. Assume those objects were > > "Employees"... you can imagine the fields would be the usual > > suspects. Assume each employee is associated with a profile that is > > another object, which is composed of a bunch of other data objects. > > > > What would you use to find/select objects like "Name or email foo > > matches > > *olson* " ? > > > > Some possibilities: > > http://jakarta.apache.org/commons/jxpath/ > > > > Some of the stuff inside Commons: > > http://jakarta.apache.org/commons/collections/ > > > > Lucene indexes > > http://jakarta.apache.org/lucene/docs/ > > > > > > Others? > > > > Tim > > > > -------------------------------------------------------------------- > > - 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
