[ 
https://issues.apache.org/jira/browse/SOLR-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174566#comment-13174566
 ] 

Lance Norskog commented on SOLR-2841:
-------------------------------------

+1

Another use case for scripting at the top level is "multi-query" queries:  
where the app creates the second based on the first. Would your proposal handle 
this problem?

Many use cases for grouping/collapsing can be implemented with 2 queries. 
Perhaps the guts of collapsing could be simplified if the more outré use cases 
could be pushed out into multiple queries.
                
> Scriptable UpdateRequestChain
> -----------------------------
>
>                 Key: SOLR-2841
>                 URL: https://issues.apache.org/jira/browse/SOLR-2841
>             Project: Solr
>          Issue Type: New Feature
>          Components: update
>            Reporter: Jan Høydahl
>
> UpdateProcessorChains must currently be defined with XML in solrconfig.xml. 
> We should explore a scriptable chain implementation with a DSL that allows 
> for full flexibility. The first step would be to make UpdateChain 
> implementations pluggable in solrconfig.xml, for backward compat support.
> Benefits and possibilities with a Scriptable UpdateChain:
> * A compact DSL for defining Processors and Chains (Workflows would be a 
> better, less limited term here)
> * Keeping update processor config separate from solrconfig.xml gives better 
> separations of roles
> * Use this as an opportunity to natively support scripting language 
> Processors (ideas from SOLR-1725)
> This issue is spun off from SOLR-2823.

--
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to