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

Deprecate types in _graph/explore calls. #40466

Merged
merged 5 commits into from
Mar 27, 2019

Conversation

jpountz
Copy link
Contributor

@jpountz jpountz commented Mar 26, 2019

Any call that uses a path that sets a type will trigger a deprecation warning.

Any call that uses a path that sets a type will trigger a deprecation warning.
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-analytics-geo

Copy link
Contributor

@jtibshirani jtibshirani left a comment

Choose a reason for hiding this comment

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

Thanks @jpountz for handling this.

I also think we should mark the HLRC GraphExploreRequest#types method as deprecated. Other than that it looks good to me.

@jpountz jpountz merged commit 8affd39 into elastic:master Mar 27, 2019
@jpountz jpountz deleted the fix/deprecate_type_in_graph_explore branch March 27, 2019 11:17
jpountz added a commit to jpountz/elasticsearch that referenced this pull request Mar 27, 2019
Any call that uses a path that sets a type will trigger a deprecation warning.
jpountz added a commit to jpountz/elasticsearch that referenced this pull request Mar 27, 2019
Any call that uses a path that sets a type will trigger a deprecation warning.
jpountz added a commit that referenced this pull request Mar 28, 2019
Any call that uses a path that sets a type will trigger a deprecation warning.
jpountz added a commit that referenced this pull request Mar 28, 2019
Any call that uses a path that sets a type will trigger a deprecation warning.
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.

4 participants