# Exclude complete path from indexing and \_source

**URL:** https://discuss.elastic.co/t/exclude-complete-path-from-indexing-and--source/37854
**Category:** Elasticsearch
**Created:** [December 23, 2015, 12:14pm UTC](https://discuss.elastic.co/t/exclude-complete-path-from-indexing-and--source/37854 "2015-12-23T12:14:23Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)
#### Post date: [January 2, 2016, 12:02pm UTC](https://discuss.elastic.co/t/exclude-complete-path-from-indexing-and--source/37854/11 "2016-01-02T12:02:09Z")

</div>

Parsing JSON and building compact JSON takes some microseconds, while network transport of unprocessed data takes at least 1000x as much, at least 5ms 🙂 But you are right, it's your decision if you want client do the work or the server, which has more important things to do, let assume searching/indexing.

---

_[View the full topic](https://discuss.elastic.co/t/exclude-complete-path-from-indexing-and--source/37854)._