Thanks for hunting that down, Jack. It may very well have been a change
that we made (to remove the stored="true". Sorry if I led you on a wild
goose chase.
Actually I wonder if people have a better method for performing config
upgrades than mine. I find that every time I take a Solr upgrade, I
need to do a point-by-point comparison of the new schema (and
solrconfiig) with my current one in order to upgrade the configuration
while keeping my custom fields, etc. plus there are all kinds of fields
in the sample schema that I don't really need: sku, manu, etc. which I
typically remove just to cut down on clutter. Does anyone have a script
that uses svn to do this in a clever way that they'd like to share?
-Mike
On 3/15/2014 4:52 PM, Jack Krupansky wrote:
Could it be that you had dropped a pre-4.2.1 schema into 4.2.1? I
mean, I just exhaustively examined all schema.xml changes between
4.2.1 and 4.6.1 (all 6 of them) and saw no wholesale change to
stored="true". Maybe somebody on your end removed a lot of fields from
the 4.2.1 release of schema.xml.
Could you give a couple of examples of fields that changed from your
4.2.1 schema?
You can examine all changes yourself here:
http://svn.apache.org/viewvc/lucene/dev/tags/lucene_solr_4_2_1/solr/example/solr/collection1/conf/schema.xml?view=log
http://svn.apache.org/viewvc/lucene/dev/tags/lucene_solr_4_6_1/solr/example/solr/collection1/conf/schema.xml?view=log
-- Jack Krupansky
-----Original Message----- From: Michael Sokolov
Sent: Saturday, March 15, 2014 1:02 PM
To: solr-user@lucene.apache.org
Subject: example schema now stores most field values
While upgrading from 4.2.1 to 4.6.1 I noticed that many of the fields
defined in the example schema.xml that used to be indexed and not stored
are now defined as indexed and stored. Is there anything behind this
change other than the idea that it would be more convenient to have all
the values available? Is it somehow cheaper to recover them from the
index now, so that storing (ints, say) is free?
-Mike
