Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of alireza.salimi@gmail.com
 designates 209.85.212.48 as permitted sender)
MIME-Version: 1.0
From: Alireza Salimi <alireza.salimi@gmail.com>
Date: Fri, 9 Mar 2012 13:24:32 -0500
Message-ID: 
 <CANUeQSfZsuudnG_UyEVyGNrHLz0b0zZ-nueMDPfYZGW0K81BNg@mail.gmail.com>
Subject: Lucene vs Solr design decision
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=bcaec5395efc35531004bad38275

--bcaec5395efc35531004bad38275
Content-Type: text/plain; charset=ISO-8859-1

Hi everybody,

Let's say we have a system with billions of small documents (average of 2-3
fields).
and each document belongs to JUST ONE user
and searches are user specific, meaning that when we search
for something, we just look into documents of that user.

On the other hand we need to see the newly added documents
as soon as they are added to the indexes.

Now I think we have two solutions:
1. Use Lucene directly and create a separate index file for each user
2. Use Solr and store all of the users' data all together in one HUGE index
file

the benefit of using Lucene is that each commit() will take less time
comparing to the case that we use Solr.

Is there any suggested solution for cases like this?

Thanks

-- 
Alireza Salimi
Java EE Developer

--bcaec5395efc35531004bad38275--