# External versioning and performance **URL:** \ **Category:** Elasticsearch\ **Created:** [May 19, 2013, 5:19pm UTC](https://discuss.elastic.co/t/external-versioning-and-performance/12028 "2013-05-19T17:19:59Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [May 19, 2013, 5:19pm UTC](https://discuss.elastic.co/t/external-versioning-and-performance/12028/1 "2013-05-19T17:19:59Z")
Hi there, Reading this: [http://www.elasticsearch.org/guide/reference/api/index\_/](http://www.elasticsearch.org/guide/reference/api/index_/) We might want to start using the epoch as the version for the stuff we index - are there any drawbacks for using such large integers as version numbers? Better safe than sorry... Thanks, Itamar -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [May 19, 2013, 9:40pm UTC](https://discuss.elastic.co/t/external-versioning-and-performance/12028/2 "2013-05-19T21:40:03Z")
there might be a very small impact on the index size. other than that no! This is totally practical and I used it in production before. simon On Sunday, May 19, 2013 7:19:59 PM UTC+2, Itamar Syn-Hershko wrote: > Hi there, > > Reading this: [Elasticsearch Platform β€” Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/index_/) > > We might want to start using the epoch as the version for the stuff we > index - are there any drawbacks for using such large integers as version > numbers? > > Better safe than sorry... > > Thanks, > > Itamar -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [May 19, 2013, 9:41pm UTC](https://discuss.elastic.co/t/external-versioning-and-performance/12028/3 "2013-05-19T21:41:46Z")
That's great to hear! thanks On Mon, May 20, 2013 at 12:40 AM, simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com)wrote: > there might be a very small impact on the index size. other than that no! > This is totally practical and I used it in production before. > > simon > > On Sunday, May 19, 2013 7:19:59 PM UTC+2, Itamar Syn-Hershko wrote: > > > Hi there, > > > > Reading this: [http://www](http://www).**[Elasticsearch Platform β€” Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/)** > > reference/api/index\_/[http://www.elasticsearch.org/guide/reference/api/index\_/](http://www.elasticsearch.org/guide/reference/api/index_/) > > > > We might want to start using the epoch as the version for the stuff we > > index - are there any drawbacks for using such large integers as version > > numbers? > > > > Better safe than sorry... > > > > Thanks, > > > > Itamar > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [May 20, 2013, 1:10pm UTC](https://discuss.elastic.co/t/external-versioning-and-performance/12028/4 "2013-05-20T13:10:27Z")
Simon, is there a way to know what was the previous version number of a document when indexing using external version type (without querying for it)? We need a way to know whether the indexing operation overrode an existing document or not. Currently we do this by simply checking if indexResponse.getVersion == 1 (meaning, this was a fresh insert). Maybe the indexResponse when using external versioning should return the previous version number, or 0 if it didn't exist? I'm using 0.90 On Mon, May 20, 2013 at 12:40 AM, simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com)wrote: > there might be a very small impact on the index size. other than that no! > This is totally practical and I used it in production before. > > simon > > On Sunday, May 19, 2013 7:19:59 PM UTC+2, Itamar Syn-Hershko wrote: > > > Hi there, > > > > Reading this: [http://www](http://www).**[Elasticsearch Platform β€” Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/)** > > reference/api/index\_/[http://www.elasticsearch.org/guide/reference/api/index\_/](http://www.elasticsearch.org/guide/reference/api/index_/) > > > > We might want to start using the epoch as the version for the stuff we > > index - are there any drawbacks for using such large integers as version > > numbers? > > > > Better safe than sorry... > > > > Thanks, > > > > Itamar > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [May 20, 2013, 6:50pm UTC](https://discuss.elastic.co/t/external-versioning-and-performance/12028/5 "2013-05-20T18:50:24Z")
I don't think there is a way to do this at this point. The cheapest way seems to be using HEAD curl -XHEAD '[http://localhost:9200/twitter/tweet/1](http://localhost:9200/twitter/tweet/1)' this has only http overhead, the version needs to be loaded anyway if you index. simon On Monday, May 20, 2013 3:10:27 PM UTC+2, Itamar Syn-Hershko wrote: > Simon, is there a way to know what was the previous version number of a > document when indexing using external version type (without querying for > it)? > > We need a way to know whether the indexing operation overrode an existing > document or not. Currently we do this by simply checking if > indexResponse.getVersion == 1 (meaning, this was a fresh insert). Maybe the > indexResponse when using external versioning should return the previous > version number, or 0 if it didn't exist? > > I'm using 0.90 > > On Mon, May 20, 2013 at 12:40 AM, simonw \<[simon.w...@elasticsearch.com](mailto:simon.w...@elasticsearch.com)\ > > > wrote: > > > there might be a very small impact on the index size. other than that no! > > This is totally practical and I used it in production before. > > > > simon > > > > On Sunday, May 19, 2013 7:19:59 PM UTC+2, Itamar Syn-Hershko wrote: > > > > > Hi there, > > > > > > Reading this: [http://www](http://www).**[Elasticsearch Platform β€” Find real-time answers at scale | Elastic](http://elasticsearch.org/guide/)** > > > reference/api/index\_/[http://www.elasticsearch.org/guide/reference/api/index\_/](http://www.elasticsearch.org/guide/reference/api/index_/) > > > > > > We might want to start using the epoch as the version for the stuff we > > > index - are there any drawbacks for using such large integers as version > > > numbers? > > > > > > Better safe than sorry... > > > > > > Thanks, > > > > > > Itamar > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [May 20, 2013, 9:40pm UTC](https://discuss.elastic.co/t/external-versioning-and-performance/12028/6 "2013-05-20T21:40:16Z")
This is one extra HTTP request I would like to avoid - we are going to do this for every one of the many docs we push hourly What I was thinking is this: When indexing, you get back in the response the version number that was assigned to the document you put. This makes sense, and quite useful in many scenarios - for example in ours, where we check to see if it == 1 and if it does we know its a new entry and can do perform some extra actions. When specifying a version yourself by using the external version type, you already know what version to expect in the response if the indexing operation succeeds. Hence, the version returned is quite meaningless. In this scenario, I would really like to get the PREVIOUS version. For us this would mean knowing whether this is a new entry or not. As far as I'm concerned, even an indication if this was an update or an insert is just fine. I'll be happy to provide a pull request with this change if this helps πŸ™‚ On Mon, May 20, 2013 at 9:50 PM, simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com)wrote: > I don't think there is a way to do this at this point. The cheapest way > seems to be using HEAD > > curl -XHEAD '[http://localhost:9200/twitter/tweet/1](http://localhost:9200/twitter/tweet/1)' > > this has only http overhead, the version needs to be loaded anyway if you > index. > > simon > > On Monday, May 20, 2013 3:10:27 PM UTC+2, Itamar Syn-Hershko wrote: > > > Simon, is there a way to know what was the previous version number of a > > document when indexing using external version type (without querying for > > it)? > > > > We need a way to know whether the indexing operation overrode an existing > > document or not. Currently we do this by simply checking if > > indexResponse.getVersion == 1 (meaning, this was a fresh insert). Maybe the > > indexResponse when using external versioning should return the previous > > version number, or 0 if it didn't exist? > > > > I'm using 0.90 > > > > On Mon, May 20, 2013 at 12:40 AM, simonw \wrote: > > > > > there might be a very small impact on the index size. other than that > > > no! This is totally practical and I used it in production before. > > > > > > simon > > > > > > On Sunday, May 19, 2013 7:19:59 PM UTC+2, Itamar Syn-Hershko wrote: > > > > > > > Hi there, > > > > > > > > Reading this: [http://www](http://www). **elasticsearch**.org/guide/ **reference/api/** > > > > index\_/ [http://www.elasticsearch.org/guide/reference/api/index\_/](http://www.elasticsearch.org/guide/reference/api/index_/) > > > > > > > > We might want to start using the epoch as the version for the stuff we > > > > index - are there any drawbacks for using such large integers as version > > > > numbers? > > > > > > > > Better safe than sorry... > > > > > > > > Thanks, > > > > > > > > Itamar > > > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send > > > an email to elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com). > > > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out) > > > . > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [May 21, 2013, 10:02am UTC](https://discuss.elastic.co/t/external-versioning-and-performance/12028/7 "2013-05-21T10:02:12Z")
On Monday, May 20, 2013 11:40:16 PM UTC+2, Itamar Syn-Hershko wrote: > This is one extra HTTP request I would like to avoid - we are going to do > this for every one of the many docs we push hourly I know πŸ™‚ I agree as well... why don't you open an issue for this? simon > What I was thinking is this: > > When indexing, you get back in the response the version number that was > assigned to the document you put. This makes sense, and quite useful in > many scenarios - for example in ours, where we check to see if it == 1 and > if it does we know its a new entry and can do perform some extra actions. > > When specifying a version yourself by using the external version type, you > already know what version to expect in the response if the indexing > operation succeeds. Hence, the version returned is quite meaningless. In > this scenario, I would really like to get the PREVIOUS version. For us this > would mean knowing whether this is a new entry or not. > > As far as I'm concerned, even an indication if this was an update or an > insert is just fine. > > I'll be happy to provide a pull request with this change if this helps πŸ™‚ > > On Mon, May 20, 2013 at 9:50 PM, simonw \<[simon.w...@elasticsearch.com](mailto:simon.w...@elasticsearch.com)\ > > > wrote: > > > I don't think there is a way to do this at this point. The cheapest way > > seems to be using HEAD > > > > curl -XHEAD '[http://localhost:9200/twitter/tweet/1](http://localhost:9200/twitter/tweet/1)' > > > > this has only http overhead, the version needs to be loaded anyway if you > > index. > > > > simon > > > > On Monday, May 20, 2013 3:10:27 PM UTC+2, Itamar Syn-Hershko wrote: > > > > > Simon, is there a way to know what was the previous version number of a > > > document when indexing using external version type (without querying for > > > it)? > > > > > > We need a way to know whether the indexing operation overrode an > > > existing document or not. Currently we do this by simply checking if > > > indexResponse.getVersion == 1 (meaning, this was a fresh insert). Maybe the > > > indexResponse when using external versioning should return the previous > > > version number, or 0 if it didn't exist? > > > > > > I'm using 0.90 > > > > > > On Mon, May 20, 2013 at 12:40 AM, simonw \ > > > > > > wrote: > > > > > > > there might be a very small impact on the index size. other than that > > > > no! This is totally practical and I used it in production before. > > > > > > > > simon > > > > > > > > On Sunday, May 19, 2013 7:19:59 PM UTC+2, Itamar Syn-Hershko wrote: > > > > > > > > > Hi there, > > > > > > > > > > Reading this: [http://www](http://www). **elasticsearch**.org/guide/\*_reference/api/_ > > > > > \*index\_/ [http://www.elasticsearch.org/guide/reference/api/index\_/](http://www.elasticsearch.org/guide/reference/api/index_/) > > > > > > > > > > We might want to start using the epoch as the version for the stuff we > > > > > index - are there any drawbacks for using such large integers as version > > > > > numbers? > > > > > > > > > > Better safe than sorry... > > > > > > > > > > Thanks, > > > > > > > > > > Itamar > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com). > > > > > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out) > > > > . > > > > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "elasticsearch" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Itamar\_Syn\_Hershko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/itamar_syn_hershko/32/725_2.png) [@Itamar\_Syn\_Hershko](https://discuss.elastic.co/u/Itamar_Syn_Hershko)\ **Post date:** [May 21, 2013, 10:07am UTC](https://discuss.elastic.co/t/external-versioning-and-performance/12028/8 "2013-05-21T10:07:14Z")
> > > When indexing, you get back in the response the version number that was assigned… to the document you put. This makes sense, and quite useful in many scenarios - for example in ours, where we check to see if it == 1 and if it does we know its a new entry and can do perform some extra actions. > > When specifying a version yourself by using the external version type, you already know what version to expect in the response if the indexing operation succeeds. Hence, the version returned is quite meaningless. In this scenario, I would really like to get the PREVIOUS version. For us this would mean knowing whether this is a new entry or not. > > I'll be happy to provide a pull request with this change if this helps :) On Tue, May 21, 2013 at 1:02 PM, simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com)wrote: > On Monday, May 20, 2013 11:40:16 PM UTC+2, Itamar Syn-Hershko wrote: > > > This is one extra HTTP request I would like to avoid - we are going to do > > this for every one of the many docs we push hourly > > I know πŸ™‚ I agree as well... why don't you open an issue for this? > > simon > > > What I was thinking is this: > > > > When indexing, you get back in the response the version number that was > > assigned to the document you put. This makes sense, and quite useful in > > many scenarios - for example in ours, where we check to see if it == 1 and > > if it does we know its a new entry and can do perform some extra actions. > > > > When specifying a version yourself by using the external version type, > > you already know what version to expect in the response if the indexing > > operation succeeds. Hence, the version returned is quite meaningless. In > > this scenario, I would really like to get the PREVIOUS version. For us this > > would mean knowing whether this is a new entry or not. > > > > As far as I'm concerned, even an indication if this was an update or an > > insert is just fine. > > > > I'll be happy to provide a pull request with this change if this helps πŸ™‚ > > > > On Mon, May 20, 2013 at 9:50 PM, simonw \wrote: > > > > > I don't think there is a way to do this at this point. The cheapest way > > > seems to be using HEAD > > > > > > curl -XHEAD '[http://localhost:9200/\*\*twitter/tweet/1](http://localhost:9200/**twitter/tweet/1)' > > > > > > this has only http overhead, the version needs to be loaded anyway if > > > you index. > > > > > > simon > > > > > > On Monday, May 20, 2013 3:10:27 PM UTC+2, Itamar Syn-Hershko wrote: > > > > > > > Simon, is there a way to know what was the previous version number of a > > > > document when indexing using external version type (without querying for > > > > it)? > > > > > > > > We need a way to know whether the indexing operation overrode an > > > > existing document or not. Currently we do this by simply checking if > > > > indexResponse.getVersion == 1 (meaning, this was a fresh insert). Maybe the > > > > indexResponse when using external versioning should return the previous > > > > version number, or 0 if it didn't exist? > > > > > > > > I'm using 0.90 > > > > > > > > On Mon, May 20, 2013 at 12:40 AM, simonw \ > > > [elasticsearch.com](http://elasticsearch.com)\> wrote: > > > > > > > > > there might be a very small impact on the index size. other than that > > > > > no! This is totally practical and I used it in production before. > > > > > > > > > > simon > > > > > > > > > > On Sunday, May 19, 2013 7:19:59 PM UTC+2, Itamar Syn-Hershko wrote: > > > > > > > > > > > Hi there, > > > > > > > > > > > > Reading this: [http://www](http://www). **elasticsearch** \*\*.org/guide/\*\* > > > > > > reference/api/ **index** \_/[http://www.elasticsearch.org/guide/reference/api/index\_/](http://www.elasticsearch.org/guide/reference/api/index_/) > > > > > > > > > > > > We might want to start using the epoch as the version for the stuff > > > > > > we index - are there any drawbacks for using such large integers as version > > > > > > numbers? > > > > > > > > > > > > Better safe than sorry... > > > > > > > > > > > > Thanks, > > > > > > > > > > > > Itamar > > > > > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "elasticsearch" group. > > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > > an email to elasticsearc...@\*\*googlegroups.\*\*com. > > > > > > > > > > For more options, visit [https://groups.google.com/\*\*grou\*\*ps/opt\_out](https://groups.google.com/ **grou** ps/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out) > > > > > . > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "elasticsearch" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > > > > an email to elasticsearc...@\*\*[googlegroups.com](http://googlegroups.com). > > > > For more options, visit [https://groups.google.com/\*\*groups/opt\_out](https://groups.google.com/**groups/opt_out)[https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out) > > > > . > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:35am UTC](https://discuss.elastic.co/t/external-versioning-and-performance/12028/9 "2017-07-06T02:35:34Z")