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 the sparse_vector field type. #48315

Merged
merged 2 commits into from
Oct 23, 2019

Conversation

jtibshirani
Copy link
Contributor

We have not seen much adoption of this experimental field type, and don't see a
clear use case as it's currently designed. This PR deprecates the field type in
7.x. It will be removed from 8.0 in a follow-up PR.

We issue a deprecation warning both when parsing the sparse_vector mapping,
and when a sparse vector function is passed to a script.

@jtibshirani jtibshirani added :Search/Search Search-related issues that do not fall into other categories >deprecation v8.0.0 v7.6.0 labels Oct 21, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search (:Search/Search)

@@ -142,6 +147,8 @@ public SparseVectorFieldType fieldType() {

@Override
public void parse(ParseContext context) throws IOException {
deprecationLogger.deprecatedAndMaybeLog("sparse_vector", DEPRECATION_MESSAGE);

Copy link
Contributor

@mayya-sharipova mayya-sharipova Oct 21, 2019

Choose a reason for hiding this comment

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

should we issue a deprecation logging only when parsing a sparse_vector mapping in public Mapper.Builder<?,?> parse(..) instead of issuing it every time when parsing a document with a sparse_vector?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, sorry I asked you to review a bit too early :) I still need to fix this, plus some failing docs tests.

@jtibshirani jtibshirani force-pushed the deprecate-sparse-vector branch from efb6e84 to fa5408b Compare October 21, 2019 22:57
We have not seen much adoption of this experimental field type, and don't see a
clear use case as it's currently designed. This PR deprecates the field type in
7.x. It will be removed from 8.0 in a follow-up PR.
@jtibshirani jtibshirani force-pushed the deprecate-sparse-vector branch from fa5408b to 1372639 Compare October 21, 2019 23:51
@jtibshirani
Copy link
Contributor Author

@mayya-sharipova this is now ready for another look, apologies again for the false start!

@jtibshirani
Copy link
Contributor Author

@elasticmachine run elasticsearch-ci/packaging-sample-matrix

Copy link
Contributor

@mayya-sharipova mayya-sharipova left a comment

Choose a reason for hiding this comment

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

@jtibshirani Thanks Julie, this looks good to me, as long as we have decided to remove sparse vectors in 8.0

@jtibshirani
Copy link
Contributor Author

@elasticmachine run elasticsearch-ci/packaging-sample-matrix

1 similar comment
@jtibshirani
Copy link
Contributor Author

@elasticmachine run elasticsearch-ci/packaging-sample-matrix

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