[
https://issues.apache.org/jira/browse/SOLR-18563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18136838#comment-18136838
]
ASF subversion and git services commented on SOLR-18563:
--------------------------------------------------------
Commit 2602d6b02cb4e97c5d7773309d542d4b4b0eaeb1 in solr's branch
refs/heads/main from linslee75
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=2602d6b02cb ]
SOLR-18563: Apply additive Schema API changes without a core reload (#5194)
Co-authored-by: David Smiley <[email protected]>
> Apply additive Schema API updates without a core reload
> -------------------------------------------------------
>
> Key: SOLR-18563
> URL: https://issues.apache.org/jira/browse/SOLR-18563
> Project: Solr
> Issue Type: Improvement
> Components: Schema and Analysis
> Reporter: Li Enlai
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h
> Remaining Estimate: 0h
>
> h2. Problem
> Solr's schemaless mode adds a field without a core reload: it persists the
> managed schema and installs it with {{SolrCore#setLatestSchema()}}.
> The Schema API does not. {{add-field}}, {{add-dynamic-field}} and
> {{add-copy-field}} reload every core using the configset. Reload replaces the
> {{IndexWriter}} and waits for running merges, so indexing pauses until those
> merges finish. On a small index the pause is short. It lasts as long as the
> merges already running.
> h2. Proposed change
> When a request contains only {{add-field}}, {{add-dynamic-field}} and
> {{add-copy-field}}, do what schemaless mode already does: persist the managed
> schema and install it with {{setLatestSchema()}}, without reloading the core.
> This writes the managed-schema znode and does not touch the configset znode,
> so the configset listener does not reload other replicas. Those replicas
> already install the schema from the managed-schema watch.
> Indexing can use the new field as soon as the command returns. In standalone
> mode the core opens a new searcher before responding, which keeps SOLR-13795.
> In SolrCloud, queries see the new field after the next commit or soft commit.
> Delete, replace, field-type and mixed requests still reload the core.
> h2. Discussion
> https://lists.apache.org/thread/3ogs0hjfw89h4w78mzm8rsfpzgdkx2r6
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
