# Entity-Centric Indexing - reliability and performance

**URL:** <https://discuss.elastic.co/t/entity-centric-indexing-reliability-and-performance/93374>\
**Category:** Elasticsearch\
**Created:** [July 17, 2017, 10:23am UTC](https://discuss.elastic.co/t/entity-centric-indexing-reliability-and-performance/93374 "2017-07-17T10:23:31Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![Mark\_Harwood](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mark_harwood/32/10538_2.png) [@Mark\_Harwood](https://discuss.elastic.co/u/Mark_Harwood)\
**Post date:** [July 19, 2017, 8:00am UTC](https://discuss.elastic.co/t/entity-centric-indexing-reliability-and-performance/93374/15 "2017-07-19T08:00:11Z")

</div>

> [@TimWard](#):
>
> it doesn't appear to have is any answer/workaround

I sincerely hope this isn't how it's done:

> [@Creation and update timestamps for each doc?](https://discuss.elastic.co/t/creation-and-update-timestamps-for-each-doc/93456/2):
>
> You could try to create an ingest pipeline for setting the created and updated timestamps, in a pipeline you can both add new document fields and modify old ones. Ref: [https://www.elastic.co/guide/en/elasticsearch/reference/5.5/put-pipeline-api.html](https://www.elastic.co/guide/en/elasticsearch/reference/5.5/put-pipeline-api.html) You can create fairly complex scripts using the painless scripting language inside such pipelines. Here's an example of a pipeline we use at my company for setting the processing time on our documents: { "description" : "Sets the document process…

---

_[View the full topic](https://discuss.elastic.co/t/entity-centric-indexing-reliability-and-performance/93374)._