# No for store, disable for \_source **URL:** \ **Category:** Elasticsearch\ **Created:** [May 31, 2013, 4:20pm UTC](https://discuss.elastic.co/t/no-for-store-disable-for--source/12211 "2013-05-31T16:20:20Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Andrew\_Gaydenko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_gaydenko/32/914_2.png) [@Andrew\_Gaydenko](https://discuss.elastic.co/u/Andrew_Gaydenko)\ **Post date:** [May 31, 2013, 4:20pm UTC](https://discuss.elastic.co/t/no-for-store-disable-for--source/12211/1 "2013-05-31T16:20:20Z")
In response to query I'd want to get just a (filtered, limited, sifted, sorted... - common search attributes) list of documents' ids. So, I plan to use "store": "no" for all fields is my document mapping (except for id) and "\_source":{ "enabled":false }. I hope such minimalistic scheme will not prevent to change the index on document updating or removing. Am I right? Are there some "side effects" we all need to know when such "id-oriented" configuration is in use? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:33am UTC](https://discuss.elastic.co/t/no-for-store-disable-for--source/12211/2 "2017-07-06T02:33:33Z")