Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Thu, 12 Jul 2012 10:43:24 -0700 (PDT)
From: Chris Hostetter <hossman_lucene@fucit.org>
To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Subject: Re: multiValued false->true
In-Reply-To: <4FFED61A.6090605@yahoo.com>
Message-ID: <alpine.DEB.2.02.1207121041070.20121@frisbee>
References: <4FFED61A.6090605@yahoo.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


: I have an indexed, not stored, not multiValued field in the schema.
: 
: If I change this field to be multiValued, would I need to re-index
: everything, or would all existing documents (that were indexed while
: the field was not multiValued) still be queryable?

usually a change like this is fine ... the existing indexed 
values will still be searchable.

when a change like this may not work the work the way you'd expect is 
if you have some special plugin (like an update processor for example) 
that changes behavior based on wether a field is multivalued or not -- 
your existing indexed values will still be there and still be searchable, 
but the index you have may not be the same as the index you'd have if you 
rebuilt from scratch after making the schema change.


-Hoss