You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Mike Klaas (JIRA)" <ji...@apache.org> on 2007/05/07 21:36:15 UTC
[jira] Commented: (SOLR-225) Allow pluggable Highlighting classes
-- Formatters and Fragmenters
[ https://issues.apache.org/jira/browse/SOLR-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494113 ]
Mike Klaas commented on SOLR-225:
---------------------------------
Wow, that is some honking configurability! I've looked at the patch, but haven't tested it.
The plugin architecture seems like something tha could be made more general than just plugins. I imagine that with very little effort, this could be used to entirely replace the *Factory.java classes that are used for Analyzer/TokenStream configuration (of course, that would relegate our nice configuration parameter names to a<lst name="defaults"> approach... perhaps the plugin archtecture could convert all unknown xml node parameters to SolrParams too?). This is a weighty-enough topic that it should perhaps be broken out into a separate issue.
The highlighting configurability itself is fine with me. I think that we'll be using the lucene highlighter (or reasonable facsimile) for long enough to make it worth additional configurability.
> Allow pluggable Highlighting classes -- Formatters and Fragmenters
> ------------------------------------------------------------------
>
> Key: SOLR-225
> URL: https://issues.apache.org/jira/browse/SOLR-225
> Project: Solr
> Issue Type: Improvement
> Reporter: Brian Whitman
> Attachments: SOLR-225-HighlightingConfig.patch
>
>
> Highlighting should support a pluggable architecture similar to what is seen with RequestHandlers, Fields, FieldTypes, etc
> '
> For more background:
> http://www.nabble.com/Custom-fragmenter-tf3681588.html#a10289335
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.