Menu
I am new to Elasticsearch with a very basic question to ask;
I am planning to use Elasticsearch as a document store and with storing documents, one of the requirements I have is to maintain historical data as well.
So I can post documents to Elasticsearch successfully, but when I post an updated version of the same document - as I've seen - original copy is overwritten. What I need is to have Elasticsearch keep older copies stored as well which I should be able to access via specifying a version number.
I have looked at its native support for document versioning which works great for concurrency control but doesn't look like it keeps a history of previous versions and only the latest version is available.
Could someone guide me in the right direction here please.
213
Elasticsearch stores data as JSON documents. Each document correlates a set of keys (names of fields or properties) with their corresponding values (strings, numbers, Booleans, dates, arrays of values, geolocations, or other types of data).
Elasticsearch is a distributed document store. Instead of storing information as rows of columnar data, Elasticsearch stores complex data structures that have been serialized as JSON documents.
You could have one document per product or one document per order. There is no limit to how many documents you can store in a particular index.
Elasticsearch engine is great option for storing unstructured data to search with Haystack. Developers love Elasticsearch (ES) for its ease of use, scalability, and the speed with which it returns keyword-based search results, even from large datasets.
As stated in here ES do not store older versions.
Note that Elasticsearch do not store older versions of documents. Only the current version can be retrieved.
You should store the history in a separate index. And insert into the history index on every update to the original document index.
138
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
