Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 66214 invoked from network); 2 Sep 2006 09:15:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Sep 2006 09:15:21 -0000 Received: (qmail 80070 invoked by uid 500); 2 Sep 2006 09:15:15 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 80048 invoked by uid 500); 2 Sep 2006 09:15:15 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 80036 invoked by uid 99); 2 Sep 2006 09:15:15 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Sep 2006 02:15:15 -0700 X-ASF-Spam-Status: No, hits=2.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of hefest@gmail.com designates 66.249.82.232 as permitted sender) Received: from [66.249.82.232] (HELO wx-out-0506.google.com) (66.249.82.232) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 02 Sep 2006 02:15:14 -0700 Received: by wx-out-0506.google.com with SMTP id s15so1319149wxc for ; Sat, 02 Sep 2006 02:14:53 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gqcCCYDDDA1Mg7ZRkmFlfGclGfJRm5+UHiF4HmvZKCIF7OyeO78R7pNUnm+YxU6tC8ysLyTLhapjtdvVrpJQCA7YVSRnEelhPPcy9xztXmQbzjaNVi8vYIIqgBvfp00wKFTztA4U0GCDMukxg0GUqR9f0PFzec+ggpronhDZlUY= Received: by 10.90.118.12 with SMTP id q12mr943512agc; Sat, 02 Sep 2006 02:14:53 -0700 (PDT) Received: by 10.90.75.3 with HTTP; Sat, 2 Sep 2006 02:14:53 -0700 (PDT) Message-ID: Date: Sat, 2 Sep 2006 11:14:53 +0200 From: "Tomi NA" To: java-user@lucene.apache.org, saurabh@danicorp.com Subject: Re: Using Lucene Index for Business Intelligence / Analytics In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 8/31/06, Saurabh Dani wrote: > > > I don't have a lot of experience with reporting tools and how data is stored by high priced tools which use OLAP and other similar storage types but we needed a solution for drill down reports and searching within large application logs / web server logs. > > So, we decided to build a reporting / analytics solution using Lucene. The product is almost ready and we are doing closed beta testing for now for reporting & searching in Web Server logs with our small set of beta customers. I am not here to promote the product or drop the URL, but wanted to get an opinion from this group on using Lucene as the data store for Business Intelligence / Analytics. > > If implemented correctly, is there any reason why a Lucene based data store cannot compete with the high priced reporting / data analytics products for drill down reports? I know about a lot of Lucene advantages which I can talk about with customers, but what can be the downside of using Lucene / competitive advantages in other products which we should be aware of? It doesn't sound promising to me. >From my own (true, not too rich) experience, search engine has as much to do with business inteligence as e.g. text processing. I mean, yes, you can probably draw an analogy of an OLAP drill-down to searching withing search results, but that's about it...reporting and analysis tools are fundamentaly different from a search engine in that they work with highly structured data and leverage that structure to do various calculations the results of which are then presented to the user. A search engine, on the other hand, is basically a tool designed to handle tons of unstructured or badly structured (i.e. structured for the human reader) data. In conclusion, you can do great things with a search engine, but BI in general or reporting in particular is not one of them. Take a look at bizgres, pentaho (mondrian, jrubik/jpivot, kettle, weka), and jasperreports to get a better idea of what I'm talking about. Just another opinion, anyway... t.n.a. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org