Re: Does _version_ field in schema need to be indexed and/or stored?

On Tue, Oct 25, 2016 at 6:41 PM, Brent wrote: > I know that in the sample config sets, the _version_ field is indexed and not > stored, like so: > > > > Is there any reason it needs to be indexed? It may depend on your solr version, but the starting configsets currently

Re: Does _version_ field in schema need to be indexed and/or stored?

Did you try using optimistic concurrency or SolrCloud? It should NOT work if I understand what's going on correctly. And if you don't index and don't store (and don't docValue), you don't actually have that field active. That's how the dynamicField */false/false/false works to avoid unknown

Does _version_ field in schema need to be indexed and/or stored?

I know that in the sample config sets, the _version_ field is indexed and not stored, like so: Is there any reason it needs to be indexed? I'm able to create collections and use them with it not indexed, but I wonder if it negatively impacts performance. -- View this message in context: