On Fri, Dec 5, 2008 at 5:40 AM, Laurence Rowe <[EMAIL PROTECTED]> wrote:
> 2008/12/4 Shalin Shekhar Mangar <[EMAIL PROTECTED]>:
>
>
> I think we have a slight misunderstanding here. Because there are many
> CMS processes it is possible that the same document will be updated
> concurrently (from di
2008/12/4 Shalin Shekhar Mangar <[EMAIL PROTECTED]>:
> If each CMS process has a consistent view of the data and it wishes to
> update Solr with that data, where is the question of inconsistency here?
Because it is difficult to guarantee the order of processing across a
distributed system while m
On Fri, Dec 5, 2008 at 2:42 AM, Laurence Rowe <[EMAIL PROTECTED]> wrote:
>
> We currently have a single Solr server, with a single index. There are
> a number of CMS processes distributed over a number of servers, with
> each CMS process sending an update to the Solr index when changes are
> made
Hi,
We currently have a single Solr server, with a single index. There are
a number of CMS processes distributed over a number of servers, with
each CMS process sending an update to the Solr index when changes are
made to a content object.
My concern is that a scenario is possible where a content
It is not clear how you are using Solr i.e. distributed vs single index.
Summarily, Solr does not update documents. It overwrites the old document
with the new one if an old document with the same uniqueKey exists in the
index.
Does that answer your question?
On Thu, Dec 4, 2008 at 1:46 AM, Laur
Hi,
Our CMS is distributed over a cluster and I was wandering how I can
ensure that index records of newer versions of documents are never
overwritten by older ones. Amazon AWS uses a timestamp on requests to
ensure 'eventual consistency' of operations. Is there a way to supply
a transaction ID wi
