You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ronald S. Wood (JIRA)" <ji...@apache.org> on 2016/08/24 19:36:20 UTC
[jira] [Created] (SOLR-9437) Add schema property useDocValues to
control use of docValues at query time
Ronald S. Wood created SOLR-9437:
------------------------------------
Summary: Add schema property useDocValues to control use of docValues at query time
Key: SOLR-9437
URL: https://issues.apache.org/jira/browse/SOLR-9437
Project: Solr
Issue Type: Improvement
Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 5.5.2
Reporter: Ronald S. Wood
Currently migration to docValues appears to be an all or nothing proposition, requiring a full reindexing when an existing field with indexed records gets docValues set to true. This can be a painful process for users with very large indexes.
If a new schema property called useDocValues is created (with a default of true), this can be used to allow incremental re-indexing of records.
The idea is that while docValues=true indexing docValues will happen as before, but as long as useDocValues=false, the partially indexed docValues will not be used so that searches, faceting, etc. will behave as if docValues=false.
Once the user is satisfied that all records have docValues, they can set useDocValues=true or remove the property altogether.
From what I can see in the Solr core code, where field.hasDocValues is now used to determine whether to use docValues at query time, the code can be changed to (field.hasDocValues && field.useDocValues).
I am uncertain whether any changes would be needed at the Lucene level.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org