lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <>
Subject Re: Number of values limitation in multivalued field
Date Tue, 19 Jan 2010 19:56:31 GMT
You should be able to do this no problem. Do be aware of the
maxfieldlength though, it defaults to 10,000 tokens but you
can change it in your schema.xml. Beware, there are TWO
instances of this in the schema file. See:

What do you mean by index/search performance impact? As
compared to what?

I think the impacts will be negligible when compared to putting all
the zip codes into the field at once, and search time should be
unaffected over that alternative.


On Tue, Jan 19, 2010 at 12:11 PM, SHS SOLR <> wrote:

> * Can we define a field in our schema as multiValued (with stored=false,
> indexed=true) that will hold upto 42K zipcode values associated to each
> document?
> * Is there any query time performance impact with this.
> * Is there any impact on index time.
> The number of documents we are talking here is not more than 100 right now.
> There is no requirement to facet or highlight or even show this field in
> the
> search results. We only want to enable zipcode searches that would return
> matching docs.
> Thanks,

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message