Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version Exposed as an Int32 Type #702

Closed
jayramay opened this issue Jun 5, 2014 · 2 comments
Closed

Version Exposed as an Int32 Type #702

jayramay opened this issue Jun 5, 2014 · 2 comments

Comments

@jayramay
Copy link

jayramay commented Jun 5, 2014

While indexing documents into Elasticsearch, I can pass an external version with the document being indexed. The reason I want to do this is because I can get various versions of the same document in a span of few seconds or even quicker than that and there is no way I can control the order in which these versions get indexed.

To make sure the index always reflects latest state of the document, I thought I could use the last modified datetime stamp in the document, convert it to a sortable datetime integer (e.g. dateTime.ToString("yyyyMMddHHmmssFFF") gives me 20140427101814673) and pass it on to Elasticsearch as an external version when indexing a document.

Elasticsearch provides a very clean versioning capability that fits nicely into my requirement - the problem however is that Elasticsearch.NET limits this functionality by exposing version as an integer based type which cannot take the large numbers I am trying to pass.

@Mpdreamz
Copy link
Member

@jayramay
Copy link
Author

Wow!! that was quick, thanks for fixing this 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants