Skip to content

Deprecate timestamp and ttl on index requests. #21826

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

Merged
merged 1 commit into from
Nov 29, 2016

Conversation

jpountz
Copy link
Contributor

@jpountz jpountz commented Nov 28, 2016

timestamp and ttl already emit deprecation warnings when they are set in
the mappings, but not when they are used in index requests. We should fix it so
that users are not caught by surprise when we stop accepting these parameters.

Relates #21670

`timestamp` and `ttl` already emit deprecation warnings when they are set in
the mappings, but not when they are used in index requests. We should fix it so
that users are not caught by surprise when we stop accepting these parameters.

Relates elastic#21670
@rjernst
Copy link
Member

rjernst commented Nov 28, 2016

LGTM

@clintongormley clintongormley added the :Search Foundations/Mapping Index mappings, including merging and defining field types label Nov 28, 2016
@jpountz jpountz merged commit 7dedd7c into elastic:5.x Nov 29, 2016
@jpountz jpountz deleted the deprecate_timestamp_ttl branch November 29, 2016 08:31
jpountz added a commit that referenced this pull request Nov 29, 2016
`timestamp` and `ttl` already emit deprecation warnings when they are set in
the mappings, but not when they are used in index requests. We should fix it so
that users are not caught by surprise when we stop accepting these parameters.

Relates #21670
@jpountz jpountz added the v5.1.1 label Nov 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>deprecation :Search Foundations/Mapping Index mappings, including merging and defining field types v5.1.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants