Return-Path: Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: (qmail 58152 invoked from network); 4 Feb 2011 11:29:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 Feb 2011 11:29:24 -0000 Received: (qmail 11543 invoked by uid 500); 4 Feb 2011 11:29:20 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 11234 invoked by uid 500); 4 Feb 2011 11:29:17 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 11226 invoked by uid 99); 4 Feb 2011 11:29:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Feb 2011 11:29:16 +0000 X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [66.94.238.130] (HELO web130103.mail.mud.yahoo.com) (66.94.238.130) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 04 Feb 2011 11:29:08 +0000 Received: (qmail 13657 invoked by uid 60001); 4 Feb 2011 11:28:46 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1296818926; bh=Jf3RIYINrO58A0XxPTIH7QG4FodaF1lgA6tscGrjlmM=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=VBf3SkNfIpocJyy+ettpvxIJNcCkEoxgvLpxvWM785Lq8CHhEkjYjECTVS3FKE61Xpa6842I9mKlhprWWNq3TaicUUz5TuIkzY6W2quRyk1KcVnewhapmb8Xywha+tWrRqfEFA+pYPa2OeJ5YTbqcHihXN5VkOLjrVnCdGIsspE= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=HzLL/KBjSzQhuH5vjB6G5j0l2a7LAm/noch5DvqTyzwAT2VFnfSzeaiY6rhN+yqsK+x/cKBdF/ULFehvnEg4p6CEcIc5MookWb30bcX10K1NCv0ZQElrN6w2/wGe4sU6w4GuwOlYbFKqrf42Sz9yHp+Ah0WalxgsuNT+H/wUDKY=; Message-ID: <866954.12361.qm@web130103.mail.mud.yahoo.com> X-YMail-OSG: XKiPVDQVM1np5egBr3kYPJ6ybDsEE3wr5zXXKuy4J.0BH6p p6hg- Received: from [74.73.25.254] by web130103.mail.mud.yahoo.com via HTTP; Fri, 04 Feb 2011 03:28:46 PST X-Mailer: YahooMailRC/555 YahooMailWebService/0.8.108.291010 References: <90362ECB07906C40A0297F9D5211A24323C55D9660@ITSEMBXCLUS.enterprise.gcal.ac.uk> Date: Fri, 4 Feb 2011 03:28:46 -0800 (PST) From: Otis Gospodnetic Subject: Re: DataImportHandler usage with RDF database To: solr-user@lucene.apache.org In-Reply-To: <90362ECB07906C40A0297F9D5211A24323C55D9660@ITSEMBXCLUS.enterprise.gcal.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked by ClamAV on apache.org Hi Lewis, > I am very interested in DataImportHandler. I have data stored in an RDF db and >wish to use this data to boost query results via Solr. I wish to keep this data >stored in db as I have a web app which directly maintains this db. Is it >possible to use a DataImportHandler to read RDF data from db in memory I don't think DIH can read from a triple store today. It can read from a RDBMS, RSS/Atom feeds, URLs, mail servers, maybe others... Maybe what you should be looking at is the ManifoldCF instead, although I don't think it can fetch data from triple stores today either. > without sending an index commit to Solr. As far as I can see DataImportHandler >currently supports full and delta imports which mean I would be indexing. > I don't follow what you mean by this and how it relates to the first part. > So far I have yet to find a requestHandler which is able to read then store >data in memory, then use this data elsewhere prior to returning documents via >queryResponseWriter. I think you are talking about a custom SearchComponent that reads some data from somewhere (e.g. your triple store) and then uses it at search time for something. This sounds doable, although you didn't provide details. For example, we (Sematext) have implemented custom SearchComponents for e-commerce customers where frequently-changing information about product availability was fetched from external stores and applied to search results. Otis ---- Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch Lucene ecosystem search :: http://search-lucene.com/