# Is it possible to run Siren ER to find hidden relationships between documents that are already reflected in your elasticsearch?

**URL:** https://community.siren.io/t/is-it-possible-to-run-siren-er-to-find-hidden-relationships-between-documents-that-are-already-reflected-in-your-elasticsearch/139
**Category:** Siren Platform/Investigate Tech Support Community
**Created:** [October 18, 2019, 6:24pm UTC](https://community.siren.io/t/is-it-possible-to-run-siren-er-to-find-hidden-relationships-between-documents-that-are-already-reflected-in-your-elasticsearch/139 "2019-10-18T18:24:33Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![kokoroko](https://avatars.discourse-cdn.com/v4/letter/k/e8c25b/32.png) [@kokoroko](https://community.siren.io/u/kokoroko)
#### Post date: [October 18, 2019, 6:24pm UTC](https://community.siren.io/t/is-it-possible-to-run-siren-er-to-find-hidden-relationships-between-documents-that-are-already-reflected-in-your-elasticsearch/139/1 "2019-10-18T18:24:33Z")

</div>

I dont want to insert new data, just want to reanalyze my indexs with Siren ER.  
Is it possible?

---

<div class="post-metadata">

### Author: ![Andrew\_Winter](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.siren.io/andrew_winter/32/33_2.png) [@Andrew\_Winter](https://community.siren.io/u/Andrew_Winter)
#### Post date: [October 23, 2019, 12:44pm UTC](https://community.siren.io/t/is-it-possible-to-run-siren-er-to-find-hidden-relationships-between-documents-that-are-already-reflected-in-your-elasticsearch/139/2 "2019-10-23T12:44:53Z")

</div>

Hi,

This should be possible using the [Elastic reindex API](https://www.elastic.co/guide/en/elasticsearch/reference/6.4/docs-reindex.html) to run the ER pipeline instead of at ingest time, and then use a [drop processor](https://www.elastic.co/guide/en/elasticsearch/reference/6.7/drop-processor.html) to ensure no new index is actually created.

1. Take the content of ingest2SirenWithER.json and add a drop processor to the end of the list of processors:

```auto
    ...
              ctx.remove('er_id');
              ctx.remove('er_dataSource');
              ctx.remove('er_output');
              '''
          }
        },
        {
          "drop": {}
        }
      ]
    }

```

1. In DevTools, create a named pipeline definition:

```auto
PUT _ingest/pipeline/siren-to-er
{
  "processors": [
    {
      "script": {
	  ...

```

1. Perform the reindexing using the new pipeline:

```auto
POST _reindex
{
  "source": { 
    "index": "myindex"
  },
  "dest": {
    "index": "myindex-processed",
    "pipeline": "siren-to-er"
  }
}

```

For a large index, DevTools may timeout before the \_reindex is complete and you may see:

```auto
 Failed to connect to Console's backend.
 Please check the Investigate server is up and running

```

In that case you can do the \_reindex outside DevTools in a curl command.

Please let us know if it works.

---

<div class="post-metadata">

### Author: ![jccq](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.siren.io/jccq/32/12_2.png) [@jccq](https://community.siren.io/u/jccq)
#### Post date: [October 26, 2019, 3:23pm UTC](https://community.siren.io/t/is-it-possible-to-run-siren-er-to-find-hidden-relationships-between-documents-that-are-already-reflected-in-your-elasticsearch/139/3 "2019-10-26T15:23:19Z")

</div>

We are going to support this use case explicitly (job to process data that is already indexdx ) in some of the new version likely 10.5 or 11