[
https://issues.apache.org/jira/browse/SOLR-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365793#comment-16365793
]
Erick Erickson commented on SOLR-12002:
---------------------------------------
Hmmm, were you then able to _use_ that field as you intend for things like
faceting and grouping? That message usually means you have _also_ switched
multiValued as well.
"Under the assumption that core reload should handle any schema changes without
issue," This is what Cassandra was responding to it simply isn't (and never has
been) in the design...
But it does seem that in this particular case there's room for improvement in
this entire area. Generally deleting *:* (which is what DIH clean does) and
reloading the core should start you all over again with a clean slate.
> Allow DocValue type changes without reindex
> -------------------------------------------
>
> Key: SOLR-12002
> URL: https://issues.apache.org/jira/browse/SOLR-12002
> Project: Solr
> Issue Type: Improvement
> 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]
