Impact of Large Stored fields blog post (#121)

* Create 2024-08-08-impact-of-large-stored-fields-on-apache-solr-query-performance.md New blog post added
apache · Aug 29, 2024 · 4495b42 · 4495b42
1 parent 2a1f383
commit 4495b42
Showing 1 changed file with 13 additions and 0 deletions.
diff --git a/...ts/2024-08-08-impact-of-large-stored-fields-on-apache-solr-query-performance.md b/...ts/2024-08-08-impact-of-large-stored-fields-on-apache-solr-query-performance.md
@@ -0,0 +1,13 @@
+Title: Impact of Large Stored fields on Apache Solr Query Performance
+category: solr/blogposts
+summary: This blog post analyzes the impact of large stored fields on Apache Solr query performance. Written by Elia Porciani, R&D Software Engineer at Sease.
+slug: impact-of-large-stored-fields-on-apache-solr-query-performance
+URL: blogposts/impact-of-large-stored-fields-on-apache-solr-query-performance.html
+save_as: blogposts/impact-of-large-stored-fields-on-apache-solr-query-performance.html
+
+# Impact of Large Stored fields on Apache Solr Query Performance
+
+In Solr, a field can be set as indexed and/or as stored.
+Having fields stored can be helpful in several scenarios. The downside is that their usage increases the index size and can affect the performance depending on how they are used.
+
+Take a look at this case study with huge stored field - the complete post can be read here: [Impact of Large Stored fields on Apache Solr Query Performance](https://sease.io/2022/12/impact-of-large-stored-fields-on-apache-solr-query-performance.html)