In our application we use dynamic fields and there can be about 50 of
them and there can be up to 100 million documents.
Are there any disadvantages having multivalued=true on all fields in
the schema? An admin of the application can specify dynamic fields and
if they should be indexed or stored.
at runtime.
Depending on your architecture, you don't really know what your document
looks like until you have it in a result set. For what I'm doing, that isn't
a problem.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Consequences-for-using-multivalued-on-all-fields-tp
Someone please correct me if I am wrong, but as far as I am aware index format
is identical in either case.
One benefit of allowing one to specify a field as single-valued is similar to
specifying that a field is required: Providing a safeguard that index data
conforms to requirements. So maki
You should be aware that the behavior of sorting on a multi-valued field is
undefined. After all, which of the multiple values should be used for
sorting?
So if you need sorting on the field, you shouldn't make it multi-valued.
Geert-Jan
2010/12/21 J.J. Larrea
> Someone please correct me if I a
ge
From: kenf_nc
To: solr-user@lucene.apache.org
Sent: Tue, December 21, 2010 6:07:51 AM
Subject: Re: Consequences for using multivalued on all fields
I have about 30 million documents and with the exception of the Unique ID,
Type and a couple of date fields, every document is made of dynamic f
7;
>
>
> EARTH has a Right To Life,
> otherwise we all die.
>
>
>
> - Original Message
> From: kenf_nc
> To: solr-user@lucene.apache.org
> Sent: Tue, December 21, 2010 6:07:51 AM
> Subject: Re: Consequences for using multivalued on all fields
>
>
