[
https://issues.apache.org/jira/browse/SOLR-8280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-8280:
---------------------------
Attachment: SOLR-8280.patch
After filing this, it occurred to me the original issue that lead me down this
investigation (SOLR-8271) I was also seeing failures in
ChangedSchemaMergeTest.testOptimizeDiffSchemas that i wasn't seeing with this
patch. Looking into why I realized it's because that test uses it's own
hardcoded schema(s) that are build on the fly from java code.
In this new updated patch, i tweaked them to directly refer to
SchemaSimilarityFactory, and now you can see the {{AssertionError: inform must
be called first}} getting logged, and the subsequent cc.shutdown() giving up
after a ref count mismatch on the directory factory.
This is probably a simpler test to trouble shoot why the SolrCoreAware.inform
isn't getting called properly then the cloud test, and hopefully can lead to a
fix that helps with both tests.
> TestCloudSchemaless fails weirdly if you try to use SolrCoreAware sim
> factory: SchemaSimilarityFactory
> -------------------------------------------------------------------------------------------------------
>
> Key: SOLR-8280
> URL: https://issues.apache.org/jira/browse/SOLR-8280
> Project: Solr
> Issue Type: Bug
> Affects Versions: Trunk
> Reporter: Hoss Man
> Attachments: SOLR-8280.patch, SOLR-8280.patch
>
>
> Something about the code path(s) involved in TestCloudSchemaless doesn't play
> nicely with a SimilarityFactory that is SolrCoreAware -- notably:
> SchemaSimilarityFactory.
> I discovered this while trying to implement SOLR-8271, but it can be
> reproduced trivially by modifying the
> schema-add-schema-fields-update-processor.xml file used by
> TestCloudSchemaless to refer to SchemaSimilarityFactory explicitly. Other
> cloud tests (such as CollectionReloadTest) or cloud+schemaless (ex:
> TestCloudManagedSchema) tests don't seem to demonstrate the same problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
