# Plugin to replace existing FetchPhase functionality in Elasticsearch **URL:** \ **Category:** Elasticsearch\ **Created:** [February 18, 2016, 1:07am UTC](https://discuss.elastic.co/t/plugin-to-replace-existing-fetchphase-functionality-in-elasticsearch/42086 "2016-02-18T01:07:59Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![shamak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shamak/32/7142_2.png) [@shamak](https://discuss.elastic.co/u/shamak)\ **Post date:** [February 18, 2016, 1:07am UTC](https://discuss.elastic.co/t/plugin-to-replace-existing-fetchphase-functionality-in-elasticsearch/42086/1 "2016-02-18T01:07:59Z")
Hello, I am looking to replace some existing 'fetch' functionality in the fetch phase in Elasticsearch using my own plugin. I was hoping that someone could point me to a good guide which would show me how a plugin would replace existing functionality? I have written a basic plugin with a separate end point which doesn't modify any of the existing functionality. I'm not quite sure how to go about modifying existing modules in Elasticsearch with a plugin. It seems like it is possible reading this link - [https://www.elastic.co/blog/found-elasticsearch-internals](https://www.elastic.co/blog/found-elasticsearch-internals). Basically, the idea is to add an option parameter to the search query in the URL, which would not return the \_id field back with the result. The hope is to return a large dataset of records with a doc\_values field in the document. Thanks! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:15pm UTC](https://discuss.elastic.co/t/plugin-to-replace-existing-fetchphase-functionality-in-elasticsearch/42086/2 "2017-07-05T23:15:31Z")