[ https://issues.apache.org/jira/browse/SOLR-12963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17706622#comment-17706622 ]
Chris M. Hostetter commented on SOLR-12963: ------------------------------------------- FWIW: the purpose of the schema {{version}} property is 100% to support the topic being discussed: to change the "new default" behavior of unspecified field/fieldtype options in the code in such a way that users who upgrade w/existing configsets get the same "old default" > 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 > > Time Spent: 1.5h > Remaining Estimate: 0h > > 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.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org