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

Eric Pugh resolved SOLR-112.
----------------------------
    Resolution: Not A Problem

 Closing as obsolete. This need is now met by InitParams 
(solr/core/src/java/org/apache/solr/core/InitParams.java), which lets a 
<initParams> block apply shared defaults/invariants/appends to multiple request 
handlers by path pattern — the same problem this ticket describes.   

Please do reopen if you are still interested in this.

> Hierarchical Handler Config
> ---------------------------
>
>                 Key: SOLR-112
>                 URL: https://issues.apache.org/jira/browse/SOLR-112
>             Project: Solr
>          Issue Type: Improvement
>          Components: update
>    Affects Versions: 1.3
>            Reporter: Ryan McKinley
>            Priority: Minor
>         Attachments: SOLR-112.patch
>
>
> From J.J. Larrea on SOLR-104
> 2. What would make this even more powerful would be the ability to "subclass" 
> (meaning refine and/or extend) request handler configs: If the requestHandler 
> element allowed an attribute extends="<another-requesthandler-name>" and 
> chained the SolrParams, then one could do something like:
>   <requestHandler name="search/products/all" 
> class="solr.DisMaxRequestHandler" >
>     <lst name="defaults">
>      <float name="tie">0.01</float>
>      <str name="qf">
>         text^0.5 features^1.0 name^1.2 sku^1.5 id^10.0 manu^1.1 cat^1.4
>      </str>
>      ... much more, per the "dismax" example in the sample solrconfig.xml ...
>   </requestHandler>
>   ... and replacing the "partitioned" example ...
>   <requestHandler name="search/products/instock" 
> extends="search/products/all" >
>     <lst name="appends">
>       <str name="fq">inStock:true</str>
>     </lst>
>   </requestHandler>



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to