Return-Path: Delivered-To: apmail-jakarta-lucene-user-archive@apache.org Received: (qmail 45241 invoked from network); 11 Dec 2002 14:17:38 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 11 Dec 2002 14:17:38 -0000 Received: (qmail 11733 invoked by uid 97); 11 Dec 2002 14:18:43 -0000 Delivered-To: qmlist-jakarta-archive-lucene-user@jakarta.apache.org Received: (qmail 11696 invoked by uid 97); 11 Dec 2002 14:18:43 -0000 Mailing-List: contact lucene-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Lucene Users List" Reply-To: "Lucene Users List" Delivered-To: mailing list lucene-user@jakarta.apache.org Received: (qmail 11669 invoked by uid 98); 11 Dec 2002 14:18:42 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: From: "Cohan, Sean" To: 'Lucene Users List' Subject: RE: Indexing in a CBD Environment Date: Wed, 11 Dec 2002 09:21:33 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2655.55) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N petite_abeille, please enlighten me. We will be using Oracle 9i. Another project using a similar architecture is coming up with a design for a 'Search Component'. The reason they are looking into an indexing scheme is to speed up search response time where we will have data distributed, across databases on separate boxes, related via the associative tables I talked about. Is there a better way to provide an acceptable searching mechanism using the relational database engine? Thanks. -----Original Message----- From: petite_abeille [mailto:petite_abeille@mac.com] Sent: Wednesday, December 11, 2002 2:08 AM To: Lucene Users List Subject: Re: Indexing in a CBD Environment On Wednesday, Dec 11, 2002, at 07:16 Europe/Zurich, Otis Gospodnetic wrote: > It uses Lucene as an > object store, of sort, I believe, with variuos relations between > objects (I did not look at the source, but I suspect it does this based > on the functionality it offers). Yep. The basic approach ZOE takes is to create one index per class and index the primary and foreigns key as keywords. It then query the different indexes to simulate a "relational" storage... Which is all handy, dandy... On the other hand, if you already have a relational database in the first place, there is no reason to go through this circus in the first place... > You may want to look at its source. If you are so inclined, you can check the alt.dev.szobject package for more gory details. In particular, SZIndex deals with Lucene directly. You can find the app and its source here: http://guests.evectors.it/zoe/ Cheers, PA. -- To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: