You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Thomas Wöckinger (Jira)" <ji...@apache.org> on 2019/09/26 13:59:00 UTC
[jira] [Updated] (SOLR-13795) SolrIndexSearcher still uses old
schema after schema update using schema-api
[ https://issues.apache.org/jira/browse/SOLR-13795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Wöckinger updated SOLR-13795:
------------------------------------
Labels: easyfix pull-request-available (was: easyfix)
> SolrIndexSearcher still uses old schema after schema update using schema-api
> ----------------------------------------------------------------------------
>
> Key: SOLR-13795
> URL: https://issues.apache.org/jira/browse/SOLR-13795
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: config-api, Schema and Analysis, Server, SolrJ, v2 API
> Affects Versions: 7.7.2, master (9.0), 8.2
> Reporter: Thomas Wöckinger
> Priority: Critical
> Labels: easyfix, pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When adding a new field to the schema using schema-api, the new field is not known by the current SolrIndexSearcher. In SolrCloud any core gets reloaded after the new schema is persisted, this does not happen in case of stand alone HTTP Solr server or EmbeddedSolrServer.
> So currently an additional commit is necessary to open a new SolrIndexSearcher using the new schema.
> Fix is really easy: Just reload the core!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org