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

Add doc’s sequence number + primary term to get responses #3767

Merged
merged 3 commits into from
May 28, 2019

Conversation

codebrain
Copy link
Contributor

Addresses: elastic/elasticsearch#36680

Backport to master and 7.x requires care due to naming conventions,

@@ -33,6 +33,12 @@ public interface IGetResponse<out TDocument> : IResponse where TDocument : class

[JsonProperty("_version")]
long Version { get; }

[JsonProperty("_primary_term")]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should this be long? on 6.x ? Not returned on older versions.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've looked into this, there are other areas of the code that have implemented both properties as long and not long?...

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They are implemented as long in places where a value is always returned, and as nullable in places where a value is returned only if a request parameter is provided that indicates to return it

@codebrain codebrain merged commit 202d9e8 into 6.8 May 28, 2019
codebrain added a commit that referenced this pull request May 29, 2019
* Additional Rollup Stats (#3759)
*  XPack info and usage improvements. (#3764)
* Add pretty names (and other properties) to the cluster stats response. (#3766)
* Set obsolete warning on GeoShape properties. (#3770)
* Add doc’s sequence number + primary term to get responses (#3767)
@Mpdreamz Mpdreamz deleted the feature/get-seq-no branch June 17, 2019 12:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants