From solr-user-return-148175-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Mon Jun 3 19:34:01 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 9D03618062F for ; Mon, 3 Jun 2019 21:34:01 +0200 (CEST) Received: (qmail 44061 invoked by uid 500); 3 Jun 2019 19:33:55 -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 44046 invoked by uid 99); 3 Jun 2019 19:33:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 Jun 2019 19:33:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 91AF81A438B for ; Mon, 3 Jun 2019 19:33:54 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.201 X-Spam-Level: X-Spam-Status: No, score=-0.201 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=elyograg.org Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 31RWuuflE4Wo for ; Mon, 3 Jun 2019 19:33:53 +0000 (UTC) Received: from bilbo.elyograg.org (bilbo.elyograg.org [54.67.1.252]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id AD7D85F195 for ; Mon, 3 Jun 2019 19:33:52 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by bilbo.elyograg.org (Postfix) with ESMTP id 45Hlbg6bprz7mBd for ; Mon, 3 Jun 2019 13:33:51 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elyograg.org; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=mail; t=1559590431; bh=Zm5KhspVi33F1hHLE8O3t2rJ6vfn vjmpTLAEBARFbfI=; b=TjI98Zxg6Nb17nlU0IXpnu2Hka+13ipELpftTK41S/YU Mb3fdJOVM+NdYQNMMK8uQ397tIXIL2ymdzuqAu0yjr2d9sDdIfh9M86ZkO17lqiI xgbDS3XNXay6q/VLQENsnv+phznEoUPi4tzCa/Fo/M/RXfSaAnT/U1tSjZlbM1Y= Received: from bilbo.elyograg.org ([127.0.0.1]) by localhost (bilbo@elyograg.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtWMzKuDHxGV for ; Mon, 3 Jun 2019 13:33:51 -0600 (MDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: elyograg@elyograg.org) by bilbo.elyograg.org (Postfix) with ESMTPSA id 45Hlbg4Xz1z7mBS for ; Mon, 3 Jun 2019 13:33:51 -0600 (MDT) Subject: Re: Using Solr as a Database? To: solr-user@lucene.apache.org References: <82efc2b7-e0be-e3bd-04eb-1464f8bc4fba@imixs.com> From: Shawn Heisey Message-ID: Date: Mon, 3 Jun 2019 13:33:51 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <82efc2b7-e0be-e3bd-04eb-1464f8bc4fba@imixs.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit On 6/2/2019 7:28 AM, Ralph Soika wrote: This is not intended to contradict the other replies you've gotten, only supplement them. > Now as far as I understand is solr a cluster enabled datastore which can > be used to store also all the data form our document. > The problem with relational databases was always the lack of > cloud/cluster support to get more stable data by using redundancy over > serveral nodes. At it's heart, Solr is using something you already understand -- Lucene. Certain functionality is implemented above that in Solr -- facets being probably the primary example. For the most part, if you wouldn't use Lucene for some purpose, you shouldn't use Solr for that purpose either -- because Solr is written with the Lucene API. Search is Solr's primary function, and what it is optimized to do. Any other use, even when it is possible, is probably going to be better handled by another piece of software. We have done what we can to eliminate problems that lose data, but data retention in the face of all potential problems is not one of the design goals. Things CAN go wrong that result in data loss ... while most database software is hardened against data loss from even unexpected problems. > What do you think? Is solr an alternative to store and index data > instead of useing Lucene in combination with RDBMS? In general, no. There are things databases can do that Solr can't, and some things that a database is better at than Solr is. Solr is good at search, and things related to search. If you have the system resources, putting a complete copy of your data in Solr is not necessarily a bad thing. Some amazing things can be done in the arena of data mining. The facet feature that I mentioned above tends to be very usable for that. Thanks, Shawn