Deprecation of types: How to be future proof?

cemremengu · January 31, 2018, 9:18am

I am new to elasticsearch and although many resources talk about index types, I just read that they will be removed soon (which I think is a good decision).

In the current 6.1.2 version of ES, we are still required to use types. What do you suggest to be future proof so that when types are no longer supported, we won't have any problems?

I read that in then next versions "doc" (or "_doc" ?) will be the default type name. Is it a good approach to name the types "doc" as a preparation?

dadoonet · January 31, 2018, 9:41am

Yes. Definitely.

system · February 28, 2018, 9:41am

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
ES Doc-Types are removed in future Elasticsearch	2	670	May 22, 2017
How to handle "type" while upgrading from es2.x to es6.x Elasticsearch	2	337	August 2, 2019
How to index types correctly to be prepared for the future updates Elasticsearch	2	431	October 23, 2018
Future versions of Elastic to not require field types Elasticsearch	4	427	June 1, 2017
Docs still refer to index types Elasticsearch	4	497	April 7, 2018

Deprecation of types: How to be future proof?

Related topics