[
https://issues.apache.org/jira/browse/SOLR-15343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mayya Sharipova updated SOLR-15343:
-----------------------------------
Security: (was: Public)
> For same change in schema file(new field _version_ added) ,Solr core in lower
> environment is working fine but in production solr cores failing
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-15343
> URL: https://issues.apache.org/jira/browse/SOLR-15343
> Project: Solr
> Issue Type: Bug
> Reporter: Nidhi Srivastava
> Priority: Major
>
> The project is using solr 6.6 with one core. There is one schema.xml file.
> The change was done in schema file by adding new field
> <field name="_version_" type="int" indexed="true" stored="true"
> multiValued="false"/> .
> The core has indexed data from previous import.
> After change in schema file when we tried to restart solr received error
> java.lang.NumberFormatException:java.lang.NumberFormatException: Invalid
> shift value (64) in prefixCoded bytes (is encoded value really an INT?)
>
> Issue: The same steps were followed in two environments with same core
> structure and setup
> The issue happened in production environment, but not in lower environment
> (The lower environment in exact replica of production in terms of server
> configuration and data )
> We checked all configuration files in lower environment (They are matching
> with prod)
> Both cores had indexed data when this change was done.
>
>
> Fix done in prod:
> When we reverted the schema changes and then started the solr , core was up
> and running.
> No data was corrupted either.
>
> I have referred the link
> https://issues.apache.org/jira/browse/SOLR-10806
>
> Help Needed: To understand why lower environment is running with same change
> and production environment gave error.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
