2009/10/28 Király Péter <pkir...@tesuji.eu>: > I just try to migrate from solr-2009-09-09.zip to today's nightly build. > I found that the *_i dynamic field's type remained int but its definition > became > <fieldType name="int" class="solr.TrieIntField" precisionStep="0" > omitNorms="true" positionIncrementGap="0"/> > > the older Solr schema lacks the definition of int, so I suppose, that its > class is > solr.IntField. I modified the schema in two points: > > <fieldType name="integer" class="solr.IntField" omitNorms="true"/> > <dynamicField name="*_i" type="integer" indexed="true" stored="true"/>
Normally, the only schema changes you can make without reindexing are those that are "compatible" with the query analyzers. Reindexing is your best bet.. or changing the schema to match exactly what you had in your old schema. I imagine that your field impl was SortableIntField, not IntField, but checking your old schema will tell you for sure. -Yonik http://www.lucidimagination.com > The result becames that the search result list contains such elements: > <str name="node_id_i">ERROR:SCHEMA-INDEX-MISMATCH,stringValue= G?</str> > > Another strange thing, that > http://localhost:8983/solr/select?q=london&version=1.2 > works well (with this error), but if I put &wt=json I received > > HTTP ERROR: 400 > undefined field type > > Do you have any idea? > > Péter