[
https://issues.apache.org/jira/browse/SOLR-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365700#comment-16365700
]
Cassandra Targett commented on SOLR-12002:
------------------------------------------
It's not a bug - it's entirely expected behavior. Nearly all schema changes
require reindexing data because simply changing the schema does nothing to
change the underlying data in the index. The schema is a guide to interpreting
the data, and when you change the schema without changing the data there is a
mismatch between what Solr is told to expect and what actually exists. This
limitation exists whether you use the classic schema or the managed schema: the
essential behavior of the schema in relation to the data in the index does not
change depending on the type of schema used.
I mention this is a limitation of Solr, and it's one that could possibly be
removed in some cases. Since I can't find another JIRA issue that covers this
enhancement, I'll modify this issue to be an Improvement and modify the issue
title accordingly.
> DocValue type changes misbehave without Solr restart
> ----------------------------------------------------
>
> Key: SOLR-12002
> URL: https://issues.apache.org/jira/browse/SOLR-12002
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 6.6.2
> Reporter: Marius Ghita
> Priority: Major
>
> I've made a change to our Solr schema where an existing field was changed and
> docValues="true" was added. Only doing a core reload, during reindexing (with
> the clean flag, in dataimporter) the message "Cannot change DocValues type
> from SORTED_SET to SORTED for field companyType" showed up in the logs, but
> not for all documents.
>
> Issuing a Solr restart and then reindexing fixed the issue. Under the
> assumption that core reload should handle any schema changes without issue, I
> think that this behaviour can be considered a bug.
>
> Note that I'm using the classical schema configuration (disabled managed
> schema), maybe managed schema exhibits the same behaviour but that's untested
> on my end.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
