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
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, Laurence Rowe <[EMAIL PROTECTED]> wrote:
>
>> Hi,
>>
>> Our CMS is dis
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
