On 5/10/07, joestelmach [EMAIL PROTECTED] wrote:
Yes, coordination between the main index searcher, the index writer,
and the index reader needed to delete other documents.
Can you point me to any documentation/code that describes this
implementation?
Look at SolrCore.getSearcher() and
]
To: solr-user@lucene.apache.org
Sent: Wednesday, May 9, 2007 6:32:33 PM
Subject: Re: Index Concurrency
On 5/9/07, joestelmach [EMAIL PROTECTED] wrote:
My first intuition is to give each user their own index. My thinking here is
that querying would be faster (since each user's index would be much
Yes, coordination between the main index searcher, the index writer,
and the index reader needed to delete other documents.
Can you point me to any documentation/code that describes this
implementation?
That's weird... I've never seen that.
The lucene write lock is only obtained when the
On 5/9/07, joestelmach [EMAIL PROTECTED] wrote:
My first intuition is to give each user their own index. My thinking here is
that querying would be faster (since each user's index would be much smaller
than one big index,) and, more importantly, that I would dodge any
concurrency issues stemming
Yonik,
Thanks for your fast reply.
No, not currently. Start your implementation with just a single
index... unless it is very large, it will likely be fast enough.
My index will get quite large
Solr also handles all the concurrency issues, and you should never hit
lock access timeout
On 5/9/07, joestelmach [EMAIL PROTECTED] wrote:
Does solr provide any additional concurrency control over what Lucene
provides?
Yes, coordination between the main index searcher, the index writer,
and the index reader needed to delete other documents.
In my simple testing of indexing 2,000
