# Indexing the query reslut directly to the same elasticsearch

**URL:** <https://discuss.elastic.co/t/indexing-the-query-reslut-directly-to-the-same-elasticsearch/247953>\
**Category:** Elasticsearch\
**Created:** [September 9, 2020, 5:23am UTC](https://discuss.elastic.co/t/indexing-the-query-reslut-directly-to-the-same-elasticsearch/247953 "2020-09-09T05:23:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mohammadreza\_Niknam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohammadreza_niknam/32/75286_2.png) [@Mohammadreza\_Niknam](https://discuss.elastic.co/u/Mohammadreza_Niknam)\
**Post date:** [September 9, 2020, 5:23am UTC](https://discuss.elastic.co/t/indexing-the-query-reslut-directly-to-the-same-elasticsearch/247953/1 "2020-09-09T05:23:22Z")

</div>

Hi all,  
I have only access to the Kibana (I don't have access to ES) and I was wondering whether it is possible to index the result of my query into a new index directly into the same ES? or I need to have access to ES and index it on the client-side (python, R, or Logstash)?

I would really appreciate it if you could guide me.  
Thank you so much.

jj

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 9, 2020, 5:26am UTC](https://discuss.elastic.co/t/indexing-the-query-reslut-directly-to-the-same-elasticsearch/247953/2 "2020-09-09T05:26:23Z")

</div>

Welcome to our community! 😃

You can run the query in a [reindex](https://www.elastic.co/guide/en/elasticsearch/reference/7.9/docs-reindex.html) call, and put that in your own index.

---

<div class="post-metadata">

**Author:** ![Mohammadreza\_Niknam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohammadreza_niknam/32/75286_2.png) [@Mohammadreza\_Niknam](https://discuss.elastic.co/u/Mohammadreza_Niknam)\
**Post date:** [September 9, 2020, 7:14am UTC](https://discuss.elastic.co/t/indexing-the-query-reslut-directly-to-the-same-elasticsearch/247953/3 "2020-09-09T07:14:16Z")

</div>

Thank you so much. I'm really excited to be here. I really appreciate it.

I just checked the Kibana and I realized I don't have access to Watcher for scheduling either. I just wanted to ask your opinion on the ETL process. Do you think the ETL process outside of the ELK stack is **efficient**? ( Some of my KPIs are severely complicated and I really doubt that the queries+aggregation+ painless could do the job - especially for some regular expression tasks)  
I'm aware that it depends on various variables, but ETL outside of the ELK is very different than trying to do the same task inside the ELK and of course easier.

Thank you so much again.

jj

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 9, 2020, 10:49pm UTC](https://discuss.elastic.co/t/indexing-the-query-reslut-directly-to-the-same-elasticsearch/247953/4 "2020-09-09T22:49:56Z")

</div>

Sounds like it would be easier to do outside Elasticsearch.

---

<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:** [October 7, 2020, 10:50pm UTC](https://discuss.elastic.co/t/indexing-the-query-reslut-directly-to-the-same-elasticsearch/247953/5 "2020-10-07T22:50:08Z")

</div>

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