Have a look at http://wiki.apache.org/solr/NearRealtimeSearch which will help
you (in TRUNK/4.0) with an efficient in-memory handling of NRT changes. Combine
this with CommitWithin for persisting to disk:
http://wiki.apache.org/solr/CommitWithin.
--
Jan Høydahl, search solution architect
Cominv
Yes, no changes to your existing index. No commit needed. You may want
to change your autocommit interval to about 15 mins ...
Regards,
- Nagendra Nagarajayya
http://solr-ra.tgels.org
http://rankingalgorithm.tgels.org
On 12/13/2011 7:32 AM, peter_solr wrote:
@ project: Thanks for the hints, I
@ project: Thanks for the hints, I will take a look!
@ Nagendra: Solr-RA seems very interesting! I take it that you can use it
with an existing index?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Looking-for-a-good-commit-merge-strategy-tp3582294p3582626.html
Sent from the
Peter:
You may want to take a look at Solr 3.4 with RankingAlgorithm 1.3. It has
NRT support that allows you to search in real time with updates. The
performance is about 1 docs / sec with the MBArtists index (approx 43
fields ). MBArtists index is the index of artists from musicbrainz.org in
How do you determine a duplicate?
Solr has de-duplication built in and also you may consider hashing
documents on some fields to create a consistent doc id that would be the
same for same documents and let Solr re-write them. Either approach would
reduce or eliminate the possibility of duplicates
