# Search source code and also use as store for them at the same time

**URL:** <https://discuss.elastic.co/t/search-source-code-and-also-use-as-store-for-them-at-the-same-time/219365>\
**Category:** Elasticsearch\
**Created:** [February 14, 2020, 12:47pm UTC](https://discuss.elastic.co/t/search-source-code-and-also-use-as-store-for-them-at-the-same-time/219365 "2020-02-14T12:47:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Armin\_Braun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/armin_braun/32/20092_2.png) [@Armin\_Braun](https://discuss.elastic.co/u/Armin_Braun)\
**Post date:** [February 14, 2020, 1:31pm UTC](https://discuss.elastic.co/t/search-source-code-and-also-use-as-store-for-them-at-the-same-time/219365/2 "2020-02-14T13:31:57Z")

</div>

Hi @ice3man543,

if you're worried that individual source files will be too large as single documents I think it is safe to say that you'll be fine. There is some discussion around the topic of max document size [Maximum document size](https://discuss.elastic.co/t/maximum-document-size/13086) (albeit pretty old, but the general concepts around Lucene still apply).  
Since you're searching on these files anyway, you'll have to index them in full I would assume (if you want to offer full text search on the source) so there is neither a need nor a point in storing them redundantly in another database IMO .

---

_[View the full topic](https://discuss.elastic.co/t/search-source-code-and-also-use-as-store-for-them-at-the-same-time/219365)._