[
https://issues.apache.org/jira/browse/SOLR-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367264#comment-14367264
]
Steve Rowe commented on SOLR-6141:
----------------------------------
[~shalinmangar] alerted me to {{TestCloudSchemaless}} fails he was seeing
25-30% of the time on trunk - I was able to get the same failures too, and I
see there is a Policeman Jenkins failure here:
[http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/11998/].
There is also a new {{TestBulkSchemaConcurrent}} fail:
[http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-MacOSX/2061/].
I backed out the above-described change to fully parse the remote changed
schema in {{ZkIndexSchemaReader}}, and I couldn't get {{TestCloudSchemaless}}
to fail. I think this is due to a change in the schema update lock - in the
old code, the schema update lock is shared by the old and new schema, but in
the new code, I created a new lock with the new schema.
I see the same pattern in the bulk schema api, at
{{SchemaManager.getFreshManagedSchema()}}, so I suspect that this is the source
of both test failures.
I'll switch both to sharing the schema update lock with the old schema and
beast them.
> Schema API: Remove fields, dynamic fields, field types and copy fields; and
> replace fields, dynamic fields and field types
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-6141
> URL: https://issues.apache.org/jira/browse/SOLR-6141
> Project: Solr
> Issue Type: Sub-task
> Components: Schema and Analysis
> Reporter: Christoph Strobl
> Assignee: Steve Rowe
> Labels: rest_api
> Attachments: SOLR-6141.patch, SOLR-6141.patch
>
>
> It should be possible, via the bulk schema API, to remove and replace the
> following:
> # fields
> # dynamic fields
> # field types
> # copy field directives (note: replacement is not applicable to copy fields)
> Removing schema elements that are referred to elsewhere in the schema must be
> guarded against:
> # Removing a field type should be disallowed when there are fields or dynamic
> fields of that type.
> # Removing a field should be disallowed when there are copy field directives
> that use the field as source or destination.
> # Removing a dynamic field should be disallowed when it is the only possible
> match for a copy field source or destination.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
