# Are we forced to data streams in 8.0?
**URL:** https://discuss.elastic.co/t/are-we-forced-to-data-streams-in-8-0/294090
**Category:** Beats
**Tags:** filebeat
**Created:** [January 11, 2022, 10:58pm UTC](https://discuss.elastic.co/t/are-we-forced-to-data-streams-in-8-0/294090 "2022-01-11T22:58:52Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@rugenl](https://discuss.elastic.co/u/rugenl)
#### Post date: [January 11, 2022, 10:58pm UTC](https://discuss.elastic.co/t/are-we-forced-to-data-streams-in-8-0/294090/1 "2022-01-11T22:58:52Z")
I'm researching what we need to do to get off legacy templates. For example, we have several indices like filebeat-7.14.0-index-a, filebeat-7.14.0-index-b, etc. They are different apps and different access rules. Now we let multiple legacy templates merge in priority order to create the desired index settings, filebeat-7.14.0 would merge with a lower priority, then custom settings for each as needed including ILM, different retention rules apply.
I tried using setup.template.type: component to use compostable indices and get this warning:
> DEPRECATED: do not use setup.template.type, it is deprecated, data streams will be loaded automatically Will be removed in version: 8.0.0
The default creates an index template, I wanted a component template that I could include in other index templates. My first idea is shot down in flames and I can't find any explanation. I read that data streams create hidden indices, but I still need to search on each individual index or application, never across all of them. This seems impossible in data streams.
I'm testing in 7.16.2.
Thanks
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 9, 2022, 12:59am UTC](https://discuss.elastic.co/t/are-we-forced-to-data-streams-in-8-0/294090/2 "2022-02-09T00:59:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.