Hi
Ups, sorry. I didn't recognized the answer because it was in the bulk
folder.
I though with this procedure it will be a lot faster and less overhead.
Just two lines of shell script.
What do you think?
Regards,
Peter.
This should work on Linux. The rsync based replication scripts used to
Hi,
any hints or suggestions?
Does anyone do the updating this way?
Regards,
Peter.
Hi solr community!
Is it recommended to replace the data directory of a heavy used solr
instance?
(I am aware of the http queries, but that will be too slow)
I need a fast way to push development data to pr
On Mon, Feb 15, 2010 at 3:30 PM, Peter Karich wrote:
> Hi solr community!
>
> Is it recommended to replace the data directory of a heavy used solr
> instance?
> (I am aware of the http queries, but that will be too slow)
>
> I need a fast way to push development data to production servers.
> I tr
Mihails,
Update is done as delete + re-add. You may also want to look at SOLR-139 in
Solr JIRA.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Mihails Agafonovs <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Sent: Tuesday, June
On your slave, you can run snappuller to get the latest snapshot from
master(generated by snapshooter), then run snapinstaller to notify solr
to use the updated index.
-Original Message-
From: Matt Mitchell [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 18, 2007 12:12 PM
To: solr-user@lu
No need to restart when there has been an index change...
just send a commit message and Solr will open a new searcher.
If there have been schema changes, Solr will need to be restarted.
-Yonik
On 7/18/07, Matt Mitchell <[EMAIL PROTECTED]> wrote:
Hi,
I'm currently working on an application wh