Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BF565100DE for ; Tue, 17 Dec 2013 23:33:09 +0000 (UTC) Received: (qmail 40230 invoked by uid 500); 17 Dec 2013 23:33:05 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 40175 invoked by uid 500); 17 Dec 2013 23:33:05 -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 40167 invoked by uid 99); 17 Dec 2013 23:33:05 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Dec 2013 23:33:05 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of bvijaykr@gmail.com designates 209.85.219.41 as permitted sender) Received: from [209.85.219.41] (HELO mail-oa0-f41.google.com) (209.85.219.41) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Dec 2013 23:33:00 +0000 Received: by mail-oa0-f41.google.com with SMTP id j17so7478211oag.28 for ; Tue, 17 Dec 2013 15:32:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=ebf+G88+CsRuvzyH4ROlx4aLXYe8cAOMvhvCHTrgsbE=; b=Geh8f8eBqGWDmeSEfGn7VGX5flnLObkO6bAg1fGmAokSAdqe4rRr3kYkpGSuM6bbET KBnfYd6Z24BuSPZ+T+/VPQEM1tRoW8aBODHYi3fMJx0GihhAaEN9l4E5PzE/4RVYxZeU sG9iq5A36VbvrZMsepmzNaoCXPepJhjNB/lsiqYzJtYv7HWsp29M6qjcXuKmlcmeuhV6 QLN8P48FJxpcJG9PCqWSjJao9y3cOaWpIJL6Wt10e/dY1W6GApUgEp4/5iB2ROo+pKUZ C4qEEeGWUhRgeTPn+/IsHQ148M2eqXfNKht3peJy9kQopATXwjP9NySVibtmaKs5ibuc y9UQ== X-Received: by 10.60.157.130 with SMTP id wm2mr18224691oeb.31.1387323160025; Tue, 17 Dec 2013 15:32:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.60.52.11 with HTTP; Tue, 17 Dec 2013 15:32:19 -0800 (PST) From: Vijay Balakrishnan Date: Tue, 17 Dec 2013 15:32:19 -0800 Message-ID: Subject: How do I use Solr for Search only instead of SQL Server while using RDBMS for write? To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=047d7bd6afcc2460e204edc3585d X-Virus-Checked: Checked by ClamAV on apache.org --047d7bd6afcc2460e204edc3585d Content-Type: text/plain; charset=ISO-8859-1 Hi, We use SQL Server currently.We are thinking about using technologies like Solr to speed up our search into the RDBMS-hopefully by flattening the RDBMS data into a denormalized data structure and indexed for the various queries performed by our users.This causes a mismatch between read-only search and subsequent write operation the user might perform on the returned data-an architectural smell.Right now, the search screen has a whole bunch of form fields to search to return the data from the RDBMS in a data grid below the search form.Any advise on how to handle this use case with Solr + Storm as an example (near real time of 30 mins)? Heard there is a plugin for Solr use with RDBMS's(DIH) ? Are they useful for this use case? My earlier work place had lots of issues with SQL server with regards to space. Even if we return from the denormalized dataSource through Solr, we need to provide a way for users to do Update data in the RDBMS using fields or a REST service ? The RDBMS data has to be denormalized to avoid making 14+ queries to SQL server.Pushing this data to a flat structure/dataSource for Solr to then use was what I was thinking about-not exactly real time and that is fine for our use case. Are there any AWS instances that can get me started on Solr + Storm ? TIA, Vijay --047d7bd6afcc2460e204edc3585d--