You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (Created) (JIRA)" <ji...@apache.org> on 2012/03/29 05:45:49 UTC
[jira] [Created] (SOLR-3293) Request Handler inheritance
Request Handler inheritance
---------------------------
Key: SOLR-3293
URL: https://issues.apache.org/jira/browse/SOLR-3293
Project: Solr
Issue Type: New Feature
Reporter: David Smiley
It would be useful if one Solr request handler could inherit from another. Or perhaps a mixin style so multiple could be merged in. I've wanted to do this to reduce repeating myself in solrconfig.xml RH configurations. Maybe all that's needed is one RH which provides the defaults to all the other search handlers. This feature could also be useful for establishing some defaults like for "df" and "q.op" and "f.myfieldname.facet.method".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3293) Request Handler inheritance
Posted by "Jan Høydahl (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241402#comment-13241402 ]
Jan Høydahl commented on SOLR-3293:
-----------------------------------
My thought was a super-simple approach. A RequestHandler with an {{extends}} would be initialized with a NamedList being the sum of the parent and the sub. For this to work, the parsing of <requestHandler> tags in solrconfig.xml would necessarily need to be done in correct order... Should we allow any number of levels or only one?
> Request Handler inheritance
> ---------------------------
>
> Key: SOLR-3293
> URL: https://issues.apache.org/jira/browse/SOLR-3293
> Project: Solr
> Issue Type: New Feature
> Reporter: David Smiley
>
> It would be useful if one Solr request handler could inherit from another. Or perhaps a mixin style so multiple could be merged in. I've wanted to do this to reduce repeating myself in solrconfig.xml RH configurations. Maybe all that's needed is one RH which provides the defaults to all the other search handlers. This feature could also be useful for establishing some defaults like for "df" and "q.op" and "f.myfieldname.facet.method".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3293) Request Handler inheritance
Posted by "Jan Høydahl (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241101#comment-13241101 ]
Jan Høydahl commented on SOLR-3293:
-----------------------------------
Let's explore this. I use request handler configs extensively for defining various search use cases, and they frequently share a considerable number of settings. Perhaps a simple {{<requestHandler name="foo" extends="bar"...>}} syntax would do? Then we could get pretty one-liners if just one parameter changes from the parent.
> Request Handler inheritance
> ---------------------------
>
> Key: SOLR-3293
> URL: https://issues.apache.org/jira/browse/SOLR-3293
> Project: Solr
> Issue Type: New Feature
> Reporter: David Smiley
>
> It would be useful if one Solr request handler could inherit from another. Or perhaps a mixin style so multiple could be merged in. I've wanted to do this to reduce repeating myself in solrconfig.xml RH configurations. Maybe all that's needed is one RH which provides the defaults to all the other search handlers. This feature could also be useful for establishing some defaults like for "df" and "q.op" and "f.myfieldname.facet.method".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3293) Request Handler inheritance
Posted by "David Smiley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241248#comment-13241248 ]
David Smiley commented on SOLR-3293:
------------------------------------
I suspected you would be interested in this issue, Jan.
Yes, it could be as simple as an extends attribute there. That was my initial idea. Two other questions:
* Is there an implied default inherited request handler? Here you could specify "df", "q.op", "f.myfieldname.facet.method", ...
* Could/should you be able to declare a handler that is only for extension and not for direct use? If so then how would it be declared as such?
* multiple extended request handlers resulting in mixin capability? -- e.g extends="base,foo,bar" Or is this overkill?
There is something to be said for simplicity of how it works. So maybe simply one parent, no way to prevent a search of a RH aside from avoiding a leading '/' (assuming handleSelect is disabled) which is good enough... and maybe no default extends since all the RH definitions declared in solrconfig.xml out of the box could refer to a base one.
This should be easy to implement.
> Request Handler inheritance
> ---------------------------
>
> Key: SOLR-3293
> URL: https://issues.apache.org/jira/browse/SOLR-3293
> Project: Solr
> Issue Type: New Feature
> Reporter: David Smiley
>
> It would be useful if one Solr request handler could inherit from another. Or perhaps a mixin style so multiple could be merged in. I've wanted to do this to reduce repeating myself in solrconfig.xml RH configurations. Maybe all that's needed is one RH which provides the defaults to all the other search handlers. This feature could also be useful for establishing some defaults like for "df" and "q.op" and "f.myfieldname.facet.method".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org