Oh my, I must have heard differently, I knew you were challenged and it had something to do with small, but I was way off base...;-)
Michael Oliver CTO Alarius Systems LLC 3325 N. Nellis Blvd, #1 Las Vegas, NV 89115 Phone:(702)643-7425 Fax:(520)844-1036 *Note new email changed from [EMAIL PROTECTED] -----Original Message----- From: Tim Colson [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 29, 2004 1:15 PM To: jug-discussion@tucson-jug.org Subject: RE: [jug-discussion] Searching large object graphs >But why not just use bean objects to a backend DB. Well, howabout because I explicitly posed the question as "just assume for a moment that RAM is cheap and you decided to load 100K objects into memory" instead of "I have a lot of data...what kind of thingy should I store it in... oh, and please reply with small words because I am developmentally challenged." Maybe that's why. ;-) > that matter hand write the old incremental sort and sorted search > routines. Apparently I wasn't clear -- I want to search using multiple criteria with wildcards/booleans on multiple fields, and on data in contained objects. Mostly I'd rather not waste time re-inventing wheels, and [usually] the folks on the list provide interesting food for thought. I won't bother with the flame-bait about "overly complex" and airguns. Cheers, Tim > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
