[jira] Reopened: (SOLR-281) Search Components (plugins)

["Ryan McKinley (JIRA)" <ji...@apache.org>]

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

Ryan McKinley reopened SOLR-281:
--------------------------------


The SearchComponent framework needs to allow for custom component initialization -- I previously believed this could be done from within the RequestHandler NamedList args.  In trying to use this for a custom component that needs to load a resource file, I found it is woefully inadequate.

As Yonik suggested a while back (and I disagreed with), I now think components should be loaded and initialized the same way as RequestHandlers.  That is, a top level name based registry in SolrCore that SearchHandlers can share.   For example, solrconfig.xml could declare:

{code:xml}
   <searchComponent name="query"     class="org.apache.solr.handler.component.QueryComponent" />
   <searchComponent name="facet"     class="org.apache.solr.handler.component.FacetComponent" />
   <searchComponent name="mlt"       class="org.apache.solr.handler.component.MoreLikeThisComponent" />
   <searchComponent name="highlight" class="org.apache.solr.handler.component.HighlightComponent" />
   <searchComponent name="debug"     class="org.apache.solr.handler.component.DebugComponent" />
{code}

and a SearchHandler can pick and choose what components are used with:
{code:xml}
 <requestHandler name="/search" class="solr.SearchHandler">
    <arr name="components">
      <str>query</str>
      <str>facet</str>
      <str>mlt</str>
      <str>highlight</str>
      <str>debug</str>
    </arr>
  </requestHandler>
{code}

Also, there should be a way to configure components to run before or after the standard component list without having to know and maintain what the "standard" list is.  For example, when we add field collapsing to the 'standard' options, it should not require everyone to update their solrconfig.xml

When SOLR-414 is committed, I will attach a patch using this strategy.

> Search Components (plugins)
> ---------------------------
>
>                 Key: SOLR-281
>                 URL: https://issues.apache.org/jira/browse/SOLR-281
>             Project: Solr
>          Issue Type: New Feature
>          Components: search
>    Affects Versions: 1.3
>            Reporter: Ryan McKinley
>            Assignee: Ryan McKinley
>             Fix For: 1.3
>
>         Attachments: SOLR-281-SearchComponents.patch, SOLR-281-SearchComponents.patch, SOLR-281-SearchComponents.patch, SOLR-281-SearchComponents.patch, SOLR-281-SearchComponents.patch, SOLR-281-SearchComponents.patch, SOLR-281-SearchComponents.patch, SOLR-281-SearchComponents.patch, SOLR-281-SearchComponents.patch, solr-281.patch, solr-281.patch, solr-281.patch
>
>
> A request handler with pluggable search components for things like:
>   - standard
>   - dismax
>   - more-like-this
>   - highlighting
>   - field collapsing 
> For more discussion, see:
> http://www.nabble.com/search-components-%28plugins%29-tf3898040.html#a11050274

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.