The title of this thread caught my eye... "commercial" vs open source should not matter. References / configs for any 3rd party projects (including other ASF projects) should be judged solely on their usefulness to Solr users.
-Yonik http://lucidworks.com On Mon, Sep 9, 2013 at 1:31 PM, Dawid Weiss <[email protected]> wrote: > Good point, Hoss. I'll think about it. There's actually something that > is a good candidate for such a reference -- > http://carrot2.github.io/solr-integration-strategies/ > > Perhaps it'd be better to just point people there, where there are > code samples and appropriate instructions. Thanks, > > Dawid > > > On Mon, Sep 9, 2013 at 7:26 PM, Chris Hostetter > <[email protected]> wrote: >> >> : Subject: A reference to a commercial algorithm in comments - is this all >> : right? >> >> I have no objections to the root of your concern: mentioning the >> commercial plugin, and how to activate it, in the solr config comments. >> >> >> In general though, i wonder if it would be simpler / more straight forward >> not include either the "Currently available open source algorithms..." or >> "A commercial algorithm..." sections in the example solr config at all >> and instead just have a shorter comment with a pointer to a URL (either on >> the solr wiki, or carrot2.org) that lists the Algos and the FQN people >> should use to configure them. >> >> That way there's less risk that the comment gets stale because we forget >> to update it, or confuses someone when carrot2 adds a new algo that works >> fine with Solr X.Y, but the Solr X.Y was released before that Algo was >> added, so its not mentioned in the comment, etc... All of that can be >> updated on whatever page the URL points to indepenent of the release. >> >> >> <!-- Class name of a clustering algorithm compatible with the Carrot2 >> framework. >> >> For a list of the available values for the "carrot.algorithm" >> please consult: >> >> http://project.carrot2.org/algorithms.html#solrconfig >> >> --> >> <str >> name="carrot.algorithm">org.carrot2.clustering.lingo.LingoClusteringAlgorithm</str> >> >> ? >> >> -Hoss >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
