in my use case, i don't really care about the versions of a document. i
only care about the latest version. so i was wondering if its a good idea
to disable it so that i save on space overhead of multiple versions? if so,
how do i go about it?
also, is there an api to purge all documents older than a certain
timestamp? i saw that with each document, you can associate a ttl but i
don't want to pre-commit myself to it at the time of document indexing.
instead, i want to be able to do it in an adhoc manner.
in my use case, i don't really care about the versions of a document.
i only care about the latest version. so i was wondering if its a
good idea to disable it so that i save on space overhead of multiple
versions? if so, how do i go about it?
also, is there an api to purge all documents older than a certain
timestamp? i saw that with each document, you can associate a ttl
but i don't want to pre-commit myself to it at the time of document
indexing. instead, i want to be able to do it in an adhoc manner.
Elasticsearch does not retain previous version of a document, it
merely keeps track of the revision number. Any search/get query will
return the latest version.
If you do not want to use the TTL feature, you can always supply your
own timestamp and execute a delete by (range) query.
in my use case, i don't really care about the versions of a document. i only
care about the latest version. so i was wondering if its a good idea to
disable it so that i save on space overhead of multiple versions? if so, how
do i go about it?
also, is there an api to purge all documents older than a certain timestamp?
i saw that with each document, you can associate a ttl but i don't want to
pre-commit myself to it at the time of document indexing. instead, i want to
be able to do it in an adhoc manner.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.