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

Adding deprecation info API message for sparse_vector #77381

Merged

Conversation

masseyke
Copy link
Member

@masseyke masseyke commented Sep 7, 2021

The sparse_vector type is deprecated and has been removed in 8.0. This commit adds a deprecation info API
message if we detect templates with mappings that include sparse_vector fields.
Relates #42404 #48781

@masseyke masseyke requested a review from jbaiera September 7, 2021 17:31
@elasticmachine elasticmachine added the Team:Data Management Meta label for data/management team label Sep 7, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

Copy link
Member

@jbaiera jbaiera left a comment

Choose a reason for hiding this comment

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

LGTM!

ClusterDeprecationChecks::formatDeprecatedSparseVectorMessage);
if (messages.isEmpty() == false) {
String messageForMapping =
"mappings in component template " + templateName + " contains deprecated sparse_vector fields: " +
Copy link
Member

Choose a reason for hiding this comment

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

lets surround the template name in some kind of quotations or punctuation so that it's easier to see as a resource name instead of just text

@masseyke masseyke merged commit bbe4c48 into elastic:7.x Sep 7, 2021
@masseyke masseyke deleted the feature/deprecation-info-sparse-vectors branch September 7, 2021 22:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Data Management Meta label for data/management team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants