I have figured out the problem. The schema was changed and index has been
deleted and rebuilt since then. But the index files might still contain the old
stale segments.
I replayed the situation by restoring the old data using 6.5, then do the
optimization, then upgrade the 6.6.1, and found out the error is gone.
Thanks
Sean
On 9/22/17, 12:16 AM, "Erick Erickson" <erickerick...@gmail.com> wrote:
This error is not about DocValuesAsStored, but about
multiValued=true|false. It indicates that multiValued is set to
"false" for the current index but "true" in the new schema. At least
that's my guess....
Best,
Erick
On Thu, Sep 21, 2017 at 11:56 AM, Xie, Sean <sean....@finra.org> wrote:
> Hi,
>
> When I upgrade the existing SOLR from 6.5.1 to 6.6.1, I’m getting:
> cannot change DocValues type from SORTED to SORTED_SET for field “…..”
>
> During the upgrades, there is no change on schema and schema version (we
are using schema version 1.5 so seDocValuesAsStored defaults are not taking
into affect).
>
> Not sure why this is happening.
>
> Planning to upgrade the SOLR version on other clusters, but don’t really
want to do re-index for all the data.
>
> Any suggestion?
>
> Thanks
> Sean
>
> Confidentiality Notice:: This email, including attachments, may include
non-public, proprietary, confidential or legally privileged information. If
you are not an intended recipient or an authorized agent of an intended
recipient, you are hereby notified that any dissemination, distribution or
copying of the information contained in or transmitted with this e-mail is
unauthorized and strictly prohibited. If you have received this email in
error, please notify the sender by replying to this message and permanently
delete this e-mail, its attachments, and any copies of it immediately. You
should not retain, copy or use this e-mail or any attachment for any purpose,
nor disclose all or any part of the contents to any other person. Thank you.
