Skip to content

Conversation

stevejgordon
Copy link
Contributor

In 7.11 the boxplot aggregation response includes two additional properties, lower and upper. I've added these to our type and updated the deserialization to handle these when present.

In 7.11 the boxplot aggregation response includes two additional
properties, lower and upper. I've added these to our type and updated
the deserialization to handle these when present.
Copy link
Member

@Mpdreamz Mpdreamz left a comment

Choose a reason for hiding this comment

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

LGTM,

in 7.10 we need a different fix that makes sure the formatter reads over these without assigning to new properties.

@stevejgordon
Copy link
Contributor Author

@Mpdreamz Sounds good. I'll drop the backport to 7.10 and put in a fresh PR to adjust accordingly. Would such changes to avoid the exception be needed in patches of 7.9 and earlier? Should 7.9.x client work with a 7.11.0 cluster?

@stevejgordon stevejgordon merged commit 7fd6e7a into master Nov 30, 2020
@stevejgordon stevejgordon deleted the feature/boxplot-aggregation-update branch November 30, 2020 12:34
github-actions bot pushed a commit that referenced this pull request Nov 30, 2020
In 7.11 the boxplot aggregation response includes two additional
properties, lower and upper. I've added these to our type and updated
the deserialization to handle these when present.
stevejgordon added a commit that referenced this pull request Nov 30, 2020
In 7.11 the boxplot aggregation response includes two additional
properties, lower and upper. I've added these to our type and updated
the deserialization to handle these when present.

Co-authored-by: Steve Gordon <sgordon@hotmail.co.uk>
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

Successfully merging this pull request may close these issues.

2 participants