On 25/08/2015 13:21, Simer P wrote:
http://stackoverflow.com/questions/32138845/what-is-the-best-approach-to-guarantee-commits-in-apache-solr
.
*Question:* How can I get "guarantee commits" with Apache SOLR where
persisting data to disk and visibility are both equally important ?
*Background:* We have a website which requires high end search
functionality for machine learning and also requires guaranteed commit for
financial transaction. We just want to SOLR as our only datastore to keep
things simple and *do not* want to use another database on the side.
I can't seem to find any answer to this question. The simplest solution for
a financial transaction seems to be to periodically query SOLR for the
record after it has been persisted but this can have longer wait time or is
there a better solution ?
Can anyone please suggest a solution for achieving "guaranteed commits"
with SOLR ?
Firstly, if you're asking here, you're likely to be answered here, not
on Stack Overflow.
A search engine is not a database. Although both Solr and Elasticsearch
are often used as primary stores with varying degrees of success, they
are after all search engines and designed for this use.
Cheers
Charlie
--
Charlie Hull
Flax - Open Source Enterprise Search
tel/fax: +44 (0)8700 118334
mobile: +44 (0)7767 825828
web: www.flax.co.uk
