[
https://issues.apache.org/jira/browse/SOLR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12464654
]
J.J. Larrea commented on SOLR-104:
----------------------------------
6. I may be going a little crazy with this soft-configuration concept, but
thinking about how to support the legacy
/select?qt=faceted...
format leads me to think there could be a trivial (3-line handleRequestBody)
NamedRequestHandler which uses one parameter to provide the name of another
parameter which names another requestHandler definition which it would then
invoke. With that,
<requestHandler name="select" class="solr. NamedRequestHandler">
<lst name="invariants">
<str name="handlerNameParameter">qt</str>
</lst>
<lst name="defaults">
<str name="qt">standard</str>
</lst>
</requestHandler>
would allow /select?qt=dismax... to be soft-implemented; a developer who had no
use for the non-URL-path selectors could strip it out, another developer who
wanted to use a different parameter to set the handler could define it that way.
> Update Plugins
> --------------
>
> Key: SOLR-104
> URL: https://issues.apache.org/jira/browse/SOLR-104
> Project: Solr
> Issue Type: Improvement
> Components: update
> Affects Versions: 1.2
> Reporter: Ryan McKinley
> Fix For: 1.2
>
> Attachments: HandlerRefactoring-DRAFT-SRC.zip,
> HandlerRefactoring-DRAFT-SRC.zip, HandlerRefactoring.DRAFT.patch,
> HandlerRefactoring.DRAFT.patch, HandlerRefactoring.DRAFT.zip
>
>
> The plugin framework should work for 'update' actions in addition to 'search'
> actions.
> For more discussion on this, see:
> http://www.nabble.com/Re%3A-Handling-disparate-data-sources-in-Solr-tf2918621.html#a8305828
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
