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

More consistent naming for term vector[s] #8484

Closed

Conversation

alexksikes
Copy link
Contributor

We speak of the term vectors of a document, where each field has an associated
stored term vector. Since by default we are requesting all the term vectors of
a document, the HTTP request endpoint should rather be called _termvectors
instead of _termvector. The usage of _termvector is now deprecated, as
well as the transport client call to termVector and prepareTermVector.

We speak of the term vectors of a document, where each field has an associated
stored term vector. Since by default we are requesting all the term vectors of
a document, the HTTP request endpoint should rather be called `_termvectors`
instead of `_termvector`. The usage of `_termvector` is now deprecated, as
well as the transport client call to termVector and prepareTermVector.
@jpountz
Copy link
Contributor

jpountz commented Nov 17, 2014

The change looks good to me. @clintongormley Could you just confirm that it's ok to break it for 2.0?

@clintongormley
Copy link
Contributor

@jpountz +1 - the old /_termvector URL is still supported (just not documented)

@dakrone
Copy link
Member

dakrone commented Nov 21, 2014

Shouldn't this be marked as "breaking" since it breaks the Java API compatibility?

@alexksikes
Copy link
Contributor Author

The old usage is still supported though.

@alexksikes alexksikes removed the review label Nov 21, 2014
@dakrone
Copy link
Member

dakrone commented Nov 21, 2014

Yes, for the REST side, on the Java side, TermVectorRequestBuilder became TermVectorsRequestBuilder and TermVectorResponse became TermVectorsResponse, which will cause compilation errors for Java API users

@alexksikes
Copy link
Contributor Author

On the Java client side you can still call on Client#termVector, but I agree for the other classes. So I'll mark it as breaking. Thanks!

@alexksikes alexksikes deleted the fix/tvs-consistent-naming branch November 21, 2014 13:32
@clintongormley clintongormley changed the title Term Vectors: More consistent naming for term vector[s] More consistent naming for term vector[s] Jun 6, 2015
@clintongormley clintongormley added :Search/Search Search-related issues that do not fall into other categories and removed :Term Vectors labels Feb 14, 2018
jtibshirani added a commit that referenced this pull request Nov 30, 2018
This endpoint was replaced by _termvectors (plural) in #8484. We deprecated the relevant
transport client methods, but didn't introduce a deprecation warning. My plan was to add
a deprecation warning in 6.6, and stop supporting this endpoint in 7.0.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>breaking :Search/Search Search-related issues that do not fall into other categories v2.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants