Yeah~, writing to true data store first, then write to solr. I found it is
simple to guarantee the finally consistency,
only handling two main exception bellow:
1. If failed to write to true data store，then client samply retry its
request。
2. If write true data store success，and failed to write
On 9/18/2018 8:11 PM, zhenyuan wei wrote:
Hi all,
add solr document with overwrite=false will keepping multi version
documents，
My question is ：
1. How to search newest documents？with what options？
2. How to delete old version < newest version documents?
When Solr is compilin
You are doing the right thing. Always write to the repository first, then
write to Solr. The repository is the single source of truth.
We write to the repository, then have a process that copies new items
to Solr.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my
Thanks for your explaination. @Alexandre Rafalovitch @Walter Underwood
My case is use SOLR as an Index Service of some NoSQL systems，it is
a common Requirement to
guarantee the consistency of index&source data .
There maybe TWO ways to write source data/index：
1. write index t
I think if you try hard enough, it is possible to get Solr to keep
multiple documents that would normally keep only the latest version.
They will just have different internal lucene id.
This may of course break a lot of other things like SolrCloud and
possibly facet counts.
So, I would ask the ac
No. Solr only has one version of a document. It is not a multi-version database.
Each replica will return the newest version it has.
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Sep 18, 2018, at 7:11 PM, zhenyuan wei wrote:
>
> Hi all,
>add
Hi all,
add solr document with overwrite=false will keepping multi version
documents，
My question is ：
1. How to search newest documents？with what options？
2. How to delete old version < newest version documents?
for example:
{
"id":"1002",
"name":["james"]
