Hi, I am designing an index of documents that have a large number of
fields. The JSON blob being indexed is complex and deeply nested. I
need to decide whether to cut out the complex part of the document to
improve query performance. I am not concerned about indexing
performance, it can be slow (within reason).
Will query performance be affected by a large number of fields in the
index?
The vast majority of queries will be very simple, querying on a few
terms, so that is what we want to optimize for.
No, the number of fields should not affect query performance to a degree
that you would notice.
On Tue, Jun 1, 2010 at 9:27 PM, Grant Rodgers grantr@gmail.com wrote:
Hi, I am designing an index of documents that have a large number of
fields. The JSON blob being indexed is complex and deeply nested. I
need to decide whether to cut out the complex part of the document to
improve query performance. I am not concerned about indexing
performance, it can be slow (within reason).
Will query performance be affected by a large number of fields in the
index?
The vast majority of queries will be very simple, querying on a few
terms, so that is what we want to optimize for.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.