I need to index voluminous data and i plan to shard it. The client may not
know which shard db to query. Server will take care of complete shard
management. I have done almost 50% of development with Lucene.
In case of Solr, i think the client should be aware of which core or
instance it want to communicate?
Regards
Ganesh
----- Original Message -----
From: "Erik Hatcher" <[EMAIL PROTECTED]>
To: <java-user@lucene.apache.org>
Sent: Tuesday, November 25, 2008 4:45 PM
Subject: Re: Marked for deletion
On Nov 25, 2008, at 5:00 AM, Ganesh wrote:
My index application is a separate process and my search application is
part of web ui. When User performs delete, i want to do mark for
deletion.
I think i have no other option other than to update the document, but
index app is a separate process and it uses index writer. In order to
update, I am planning to use RMI and create a single application which
does both index and search and also exposes some search and delete
methods.
Is there any other way to achieve this?
Perhaps consider using Solr if you're going to wrap Lucene with some sort
of service layer. It already takes care of the bulk of the hard stuff
that you'd end up having to deal with (warming, etc).
Erik
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Send instant messages to your online friends http://in.messenger.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
