# Life without mapping types (6.0) **URL:** \ **Category:** Elasticsearch\ **Created:** [December 1, 2017, 12:43am UTC](https://discuss.elastic.co/t/life-without-mapping-types-6-0/109858 "2017-12-01T00:43:46Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [December 1, 2017, 6:33pm UTC](https://discuss.elastic.co/t/life-without-mapping-types-6-0/109858/2 "2017-12-01T18:33:00Z")
I tried to give some thoughts in the other post you sent about this: > [@Understand and using relationships without mapping types (6.0)](https://discuss.elastic.co/t/understand-and-using-relationships-without-mapping-types-6-0/109863): > > RE: Removal of mapping types [https://www.elastic.co/guide/en/elasticsearch/reference/current/removal-of-types.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/removal-of-types.html) It looks like the proposed solution is to use a "common key" - my term. Such a common key can tie a user to a tweet, as in the example, but let's get serious, and talk about more complex, and I suspect, more common, and realistic use cases, shall we? Let's say I have a FACTORY, and I make PRODUCT. I have a supply chain of numerous different VENDORS, who sell me various PARTS, ING… --- _[View the full topic](https://discuss.elastic.co/t/life-without-mapping-types-6-0/109858)._