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

Introduce an include_type_name constant #37155

Merged
merged 1 commit into from
Jan 7, 2019

Conversation

cbuescher
Copy link
Member

I started referring to this parameter name from various places in #37149 so I
thought it's a good idea to simplify things by referring to a common constant.
If you think there are better places to put it than BaseRestHandler please suggest
alternatives. Then again, it will be there only temporarily.

I started referring to this parameter name from various places in elastic#37149 so I
think it's a good idea to simplify things by referring to a common constant.
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 @cbuescher, it will be nice to avoid hardcoding this in more places. I also can't think of a better place to put the constant.

@jtibshirani
Copy link
Contributor

One other thought: it would be good to backport this to 6.x as well, maybe after #37147 merges.

@cbuescher cbuescher added >non-issue v7.0.0 :Search Foundations/Mapping Index mappings, including merging and defining field types labels Jan 5, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search

@cbuescher cbuescher merged commit d18c3d6 into elastic:master Jan 7, 2019
@cbuescher
Copy link
Member Author

cbuescher commented Jan 7, 2019

It would be good to backport this to 6.x as well, maybe after #37147 merges.

@jtibshirani When I just looked at backporting the constant, I saw that neither of the three APIs changed here (create index, get mapping, put mapping) already use the "include_type_name" parameter on 6.x. Is the "include_type_name" backport for these APIs pending or don't we plan on supporting it? I was of the impression it is the former but wanted to confirm. Will not backport for now until the parameter is supported anywhere in 6.x.

@jtibshirani
Copy link
Contributor

Your understanding is correct -- the backport was opened in #37147 and is still pending.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>non-issue :Search Foundations/Mapping Index mappings, including merging and defining field types v7.0.0-beta1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants