# Is it good to clone & abstract a document to a new index for 1 search api?

**URL:** <https://discuss.elastic.co/t/is-it-good-to-clone-abstract-a-document-to-a-new-index-for-1-search-api/119942>\
**Category:** Elasticsearch\
**Created:** [February 15, 2018, 8:36am UTC](https://discuss.elastic.co/t/is-it-good-to-clone-abstract-a-document-to-a-new-index-for-1-search-api/119942 "2018-02-15T08:36:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![michaelcheung](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michaelcheung/32/53285_2.png) [@michaelcheung](https://discuss.elastic.co/u/michaelcheung)\
**Post date:** [February 15, 2018, 8:36am UTC](https://discuss.elastic.co/t/is-it-good-to-clone-abstract-a-document-to-a-new-index-for-1-search-api/119942/1 "2018-02-15T08:36:56Z")

</div>

Hi,

I have an index keeps on indexing docs which are my server logs (e.g. user activities, transaction activities, system jobs, etc).  
And my server needs to later query back ES by doc\_id to get a transaction's info. Should I directly query the original index?  
If I create a new index, only put transaction doc to it (clone in logstash) and query the index, is it good practice to optimize search performance?

Thanks,  
Michael

---

<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:** [March 15, 2018, 8:37am UTC](https://discuss.elastic.co/t/is-it-good-to-clone-abstract-a-document-to-a-new-index-for-1-search-api/119942/2 "2018-03-15T08:37:26Z")

</div>

Closed on March 15, 2018, 8:37am UTC

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