You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Dawid Weiss (JIRA)" <ji...@apache.org> on 2015/08/25 11:44:45 UTC

[jira] [Updated] (SOLR-7969) Unavailable clustering engines should not fail the core

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

Dawid Weiss updated SOLR-7969:
------------------------------
    Fix Version/s: Trunk

> Unavailable clustering engines should not fail the core
> -------------------------------------------------------
>
>                 Key: SOLR-7969
>                 URL: https://issues.apache.org/jira/browse/SOLR-7969
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Dawid Weiss
>            Assignee: Dawid Weiss
>            Priority: Trivial
>             Fix For: Trunk, 5.4
>
>
> Currently the clustering contrib will fail at initialization time if an algorithm (or some of its dependencies) is not available. This shouldn't be so eager, instead:
> * the declaration of an engine should allow optionality,
> * log the message about unavailable engine/algorithm (and its ID); if it is optional, the message can have a debug level,
> * fail at query-time if the engine is requested explicitly.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org