Need help in setting "uninvertible=true" in schema

[Sandeep Biswas <sa...@opentext.com.INVALID>]

Hi Everyone,

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 enabling uninvertible attribute. So, my question is, can I safely set the uninvertible attribute to true for each field in the schema? I read 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?

P.S.: docValues cannot be added at this moment as the cost of reindexing is too high. We can wait till solr 10 for reindex.

Thanks,
Sandeep

Re: Need help in setting "uninvertible=true" in schema

[Chris Hostetter <ho...@fucit.org>]

: 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/

Re: Need help in setting "uninvertible=true" in schema

[ufuk yılmaz <uy...@vivaldi.net.INVALID>]

> I read in some articles that uninversion may cause huge memory usage that can lead to crashes during facet query processing.

I think the way it worked before the default config value has changed was the same as it works now, so if it was working for you before, it should work now too? I don’t think it got more inefficient when the default value changed to false. 

—

> On Jul 24, 2025, at 22:25, Sandeep Biswas <sa...@opentext.com.invalid> wrote:
> 
> I read in some articles that uninversion may cause huge memory usage that can lead to crashes during facet query processing.