Can We Retrieve Previous _source Docs with Elastic Search Versions

by

No, you can’t do this using the builtin versioning. All that does is to store the current version number to prevent you applying updates out of order.

If you wanted to keep multiple versions available, then you’d have to implement that yourself. Depending on how many versions you are likely to want to store, you could take three approaches:

For low volume changes:

1) store older versions within the same document

{ text: "foo bar",
  date:  "2011-11-01",
  previous: [
      { date: '2011-10-01', content: { text: 'Foo Bar' }},
      { date: '2011-09-01', content: { text: 'Foo-bar!' }},
  ]
}

For high volume changes:

2) add a current flag:

{
   doc_id:  123,
   version: 3,
   text:    "foo bar",
   date:    "2011-11-01",
   current: true
}

{
   doc_id:  123,
   version: 2,
   text:    "Foo Bar",
   date:    "2011-10-01",
   current: false
}

3) Same as (2) above, but store the old versions in a separate index, so keeping your “live” index, which will be used for the majority of your queries, small and more performant.

More Related Contents:

  1. Elasticsearch replication of other system data?
  2. How to search for a part of a word with ElasticSearch
  3. no [query] registered for [filtered]
  4. elasticsearch bool query combine must with OR
  5. ElasticSearch – Return Unique Values
  6. Remove duplicate documents from a search in Elasticsearch
  7. Elasticsearch 2.1: Result window is too large (index.max_result_window)
  8. Max limit on the number of values I can specify in the ids filter or generally query clause?
  9. UTF8 encoding is longer than the max length 32766
  10. How to update multiple documents that match a query in elasticsearch
  11. Queries vs. Filters
  12. Why do I need “store”:”yes” in elasticsearch?
  13. Change default mapping of string to “not analyzed” in Elasticsearch
  14. How to not-analyze in ElasticSearch?
  15. elasticsearch – what to do with unassigned shards
  16. Elasticsearch vs Cassandra vs Elasticsearch with Cassandra
  17. FIELDDATA Data is too large
  18. Find documents with empty string value on elasticsearch
  19. Elasticsearch, Tire, and Nested queries / associations with ActiveRecord
  20. low disk watermark [??%] exceeded on
  21. ElasticSearch – Get only matching nested objects with All Top level fields in search response
  22. Elasticsearch – set max_clause_count
  23. How to bind Elasticsearch 2.0 on both Loopback and Non-Loopback interfaces?
  24. ElasticSearch: aggregation on _score field?
  25. How to parse json in logstash /grok from a text file line?
  26. Logstash: Merge two logs into one output document
  27. Remove a field from a Elasticsearch document
  28. Elasticsearch error: cluster_block_exception [FORBIDDEN/12/index read-only / allow delete (api)], flood stage disk watermark exceeded
  29. What is the ElasticSearch equivalent for an SQL subquery?
  30. How to create multiple indexes in logstash.conf file?

Leave a Comment