[
https://issues.apache.org/jira/browse/SOLR-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Chanan updated SOLR-6145:
---------------------------------
Attachment: SOLR-6145.patch
Here's a patch that fixes the test.
The basic idea is that retrying on a BadVersionException won't help the
ManagedIndexSchema, since the version will always be past our version.
Instead, we just throw an exception that can be caught by the callers and
retried. I only put the retry logic in FieldResource for now, but there's a
few more places where it should go if we like this approach.
I originally thought of doing the retry logic inside of ManagedIndexSchema, so
we wouldn't need to put it in as many places, but that seemed not as clean,
since the older schema would be getting the newer schema (presumably from the
core), which seems wrong since a schema should exist independently of a core.
> Concurrent Schema API field additions can result in endless loop
> ----------------------------------------------------------------
>
> Key: SOLR-6145
> URL: https://issues.apache.org/jira/browse/SOLR-6145
> Project: Solr
> Issue Type: Bug
> Components: Schema and Analysis
> Reporter: Steve Rowe
> Assignee: Steve Rowe
> Priority: Critical
> Attachments: SOLR-6145.patch, concurrent_updates_and_schema_api.patch
>
>
> The optimistic concurrency loop in {{ManagedIndexSchema.addFields()}} is the
> likely culprit.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
