[
https://issues.apache.org/jira/browse/SOLR-18350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18109465#comment-18109465
]
ASF subversion and git services commented on SOLR-18350:
--------------------------------------------------------
Commit aeb6712f6ff73228a997067c55f9fded7379200e in solr's branch
refs/heads/branch_10x from NextBrickINC.com
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=aeb6712f6ff ]
SOLR-18350: Live schema changes could disrupt requests in progress (#4817)
At least theoretically.
Co-authored-by: rayshrey <[email protected]>
(cherry picked from commit 812408433c661cf61c9b6d2784787304e39907bf)
> Many callers of org.apache.solr.core.SolrCore#getLatestSchema should use
> alternatives
> -------------------------------------------------------------------------------------
>
> Key: SOLR-18350
> URL: https://issues.apache.org/jira/browse/SOLR-18350
> Project: Solr
> Issue Type: Bug
> Reporter: David Smiley
> Priority: Minor
> Labels: newdev, pull-request-available
> Attachments: SOLR-18350_Technical_Brief_NextBricks_Secure.pdf
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> SolrCore.getLatestSchema can be updated at any time if a schema mutation
> happens. On the other hand, the SolrQueryRequest has a cached/stable value.
> A SolrIndexSearcher also has a cached/stable value. Code that needs the
> schema that _already_ has access to either of those in scope should use them
> to get the schema, *not* via the core. The javadocs of
> {{SolrCore.getLatestSchema}} should advise about this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
