Solr will easily handle 1,000. But note a couple of things: 1> There's no _requirement_ that you use multiValued fields. If it's a text field and you use minimal analysis, you can just shove them all into a single value. Confusing I know. MultiValued means that this is accepted (xml format of a SolrInputDoc for illustration) <doc> <field name="f1">val1</field> <field name="f1">val2</field> </doc>
But you get essentially the same thing by this if you break on whitespace only: <doc> <field name="f1">val1 val2</field> </doc> There's a subtle difference in that with the positionIncrementGap at the default 100, the term position of "val2" will be something like 102 in the first example and 2 in the second. But unless you're doing phrase queries, you'll never notice the difference between the two. 2> The cost of faceting and the like goes up with the _total_ number of unique terms in the field. So let's say you have 10 docs, each with 1,000 unique values in your field. By "unique" here I mean no two docs have any value in common. Then you have 10,000 unique values across all your docs, that's less expensive than if you have 1,000 docs no two of which have any values in common or 1,000,000 unique values. FWIW, Erick On Tue, Dec 1, 2015 at 8:20 AM, Troy Edwards <tedwards415...@gmail.com> wrote: > We are considering using a multivalued field that can contain up to 1000 > unique values. This field will not be searched on but just used in facet > and filter. > > What is the maximum number of values that a multivalued field can contain? > > Is there another more efficient way of doing this? > > Thanks
