Performance considerations for indexed nested fields

We are reaching a point where we will end up having a dozen or so indexed nested fields on each of our documents (which as we know creates an additional indexed document for each nested entry).

We're looking to understand the performance implications of this (as it will significantly increase our overall document count in our indexes), and to explore any alternatives, such as dynamically creating a different field for each nested document instead.



Hello, Ben.
Nested docs are the most perfomant data structure on Earth. Blowing up fields rather kills Lucene index.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.