: I would like to pick your brains on tackling a schema upgrade from 1.6 : to 1.7. We have our current deployment on schema 1.6, which means : uninvertible attribute for each field is true by default, hence sorting, : faceting is supported. We do not use docValues on these fields. : : Now, with the schema upgrade to 1.7, docValues=true, and : uninvertible=false by default. This means that we cannot use the : existing index, as the fields will not support sorting, faceting without
You can absolutely keep using your existing index -- with your existing schema. Just because the default configset has changed in newer versions of solr doens't mean you can't continue to use your existing configset with your existing collections. (you can even use your eixsting configsets with *new* collections if you want to) : enabling uninvertible attribute. So, my question is, can I safely set : the uninvertible attribute to true for each field in the schema? I read there is no reason to modify your schema to set "version=1.7" if you are just planning to set every individual field uninvertible=true. : in some articles that uninversion may cause huge memory usage that can : lead to crashes during facet query processing. I do have a very large : collection and many fields need to support sorting, faceting. Will it be : advisable to enable uninversion? the "cost" / risks of Un-Inverting fields has not changed. The only thing that has changed is whether *new* solr collections face those risks by default. -Hoss http://www.lucidworks.com/
