From 4495b42ebc5e15b668fe60dc7c72d6ea15e11406 Mon Sep 17 00:00:00 2001
From: Lisa <114702254+lizbiella@users.noreply.github.com>
Date: Thu, 29 Aug 2024 16:28:38 +0200
Subject: [PATCH] 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
---
 ...tored-fields-on-apache-solr-query-performance.md | 13 +++++++++++++
 1 file changed, 13 insertions(+)
 create mode 100644 content/pages/blogposts/2024-08-08-impact-of-large-stored-fields-on-apache-solr-query-performance.md

diff --git a/content/pages/blogposts/2024-08-08-impact-of-large-stored-fields-on-apache-solr-query-performance.md b/content/pages/blogposts/2024-08-08-impact-of-large-stored-fields-on-apache-solr-query-performance.md
new file mode 100644
index 000000000..311a894db
--- /dev/null
+++ b/content/pages/blogposts/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)