[
https://issues.apache.org/jira/browse/SOLR-13795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944668#comment-16944668
]
ASF subversion and git services commented on SOLR-13795:
--------------------------------------------------------
Commit 22e96697de1d9bc710f6e68e94885460106528bc in lucene-solr's branch
refs/heads/master from Thomas Wöckinger
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=22e9669 ]
SOLR-13795: Managed schema should do a core reload in standalone mode.
Fixes #902
> 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
> Assignee: David Wayne Smiley
> Priority: Critical
> Labels: easyfix, pull-request-available
> Time Spent: 3h 20m
> 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: [email protected]
For additional commands, e-mail: [email protected]
