[
https://issues.apache.org/jira/browse/SOLR-12963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191849#comment-17191849
]
Alexandre Rafalovitch commented on SOLR-12963:
----------------------------------------------
Could we implement this for 9 (version bump and default change)? I just checked
both our default configsets and we don't have this field actually set to false
anywhere. So, we are not following our own RefGuide "strongly encouraged"
advice.
Also, we also have 3 instances of *uninvertable* in the codebase, fortunately
just in comments.
> change default for 'uninvertible' to 'false' (dependent on new schema
> 'version')
> --------------------------------------------------------------------------------
>
> Key: SOLR-12963
> URL: https://issues.apache.org/jira/browse/SOLR-12963
> Project: Solr
> Issue Type: Sub-task
> Reporter: Chris M. Hostetter
> Priority: Major
> Attachments: SOLR-12963.patch
>
>
> We should consider changing the default behavior of the {{uninvertible}}
> field option to be dependnt on the schema {{version}} property, such that
> moving forward the fields/fieldtypes will default to {{uninvertible ==
> false}} unless an explicit {{uninvertible=true}} is specified by the user.
> There are a lot of considerations regarding the existing behavior of
> functionality (like faceting) when the (effective) value of {{uninvertible}}
> is false because we move forward with changing this in a way that could
> suprise/confuse new users or existing users w/ long heald expectations that
> certain behavior would just "work" w/o understanding that was because of
> FieldCache/uninversion.
> See parent issue for more background/discussion.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
