[ 
https://issues.apache.org/jira/browse/SOLR-8280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man updated SOLR-8280:
---------------------------
             Assignee: Hoss Man
    Affects Version/s:     (was: Trunk)
                       5.0
        Fix Version/s: Trunk
                       5.4
          Description: 
SOLR-8271 uncovered problems with using SchemaSimilarityFactory + schemaless 
features.  While the broader problems of SolrCoreAware objects inited after the 
SolrCore was live have been spun off into SOLR-8311 this issue focuses on 
fixing & testing the core problem of ensuring SchemaSimilarityFactory + 
schemaless features function together.

{panel:title=original bug report}
Something about the code path(s) involved in TestCloudSchemaless & 
ChangedSchemaMergeTest don'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 (and hardcoded in java schema used by 
ChangedSchemaMergeTest) 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.
{panel}

  was:
Something about the code path(s) involved in TestCloudSchemaless & 
ChangedSchemaMergeTest don'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 (and hardcoded in java schema used by 
ChangedSchemaMergeTest) 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.


              Summary: Schemaless features don't work reliably with 
SolrCoreAware sim factory -- example: SchemaSimilarityFactory  (was: 
TestCloudSchemaless + ChangedSchemaMergeTest fail weirdly if you try to use 
SolrCoreAware sim factory: SchemaSimilarityFactory )

> Schemaless features don't work reliably with SolrCoreAware sim factory -- 
> example: SchemaSimilarityFactory
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-8280
>                 URL: https://issues.apache.org/jira/browse/SOLR-8280
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 5.0
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>             Fix For: 5.4, Trunk
>
>         Attachments: SOLR-8280.patch, SOLR-8280.patch, SOLR-8280.patch, 
> SOLR-8280.patch, SOLR-8280__broken__resource_loader_experiment.patch
>
>
> SOLR-8271 uncovered problems with using SchemaSimilarityFactory + schemaless 
> features.  While the broader problems of SolrCoreAware objects inited after 
> the SolrCore was live have been spun off into SOLR-8311 this issue focuses on 
> fixing & testing the core problem of ensuring SchemaSimilarityFactory + 
> schemaless features function together.
> {panel:title=original bug report}
> Something about the code path(s) involved in TestCloudSchemaless & 
> ChangedSchemaMergeTest don'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 (and hardcoded in java schema used by 
> ChangedSchemaMergeTest) 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.
> {panel}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to