# Read Only Index Creation - Force Single Segment

**URL:** <https://discuss.elastic.co/t/read-only-index-creation-force-single-segment/2038>\
**Category:** Elasticsearch\
**Created:** [June 5, 2015, 6:25pm UTC](https://discuss.elastic.co/t/read-only-index-creation-force-single-segment/2038 "2015-06-05T18:25:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mtraynham](https://avatars.discourse-cdn.com/v4/letter/m/fbc32d/32.png) [@mtraynham](https://discuss.elastic.co/u/mtraynham)\
**Post date:** [June 5, 2015, 6:25pm UTC](https://discuss.elastic.co/t/read-only-index-creation-force-single-segment/2038/1 "2015-06-05T18:25:02Z")

</div>

Is there a way during index creation to force it only to create a single segment? I'm using the elasticsearch-hadoop package with Hive calls. The indices are usually 10 MB - 50 MB in size, and are never updated or deleted from. The reason I ask is it would seem more performant than an \_optimize call after creation.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 12:09am UTC](https://discuss.elastic.co/t/read-only-index-creation-force-single-segment/2038/2 "2017-07-06T00:09:22Z")

</div>

Closed on July 6, 2017, 12:09am UTC