[
https://issues.apache.org/jira/browse/SOLR-6892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259422#comment-14259422
]
Alexandre Rafalovitch commented on SOLR-6892:
---------------------------------------------
So, would the better explanation be then is that you have an option of
pre-configuring and naming individual items on the stack and then composing
them either in pre-existing stack (effectively with aliases) or dynamically on
the fly.
So, the addressable unit becomes an individual pre-configured URP (atom) as
opposed to the full stack (molecule)?
That would make more sense, though you still need to be super-clear on what
becomes hidden from the XML file. For example, there should be an easy way to
query all the pre-configured components. One of the issues with ElasticSearch
is that it is hard to tell what those symbolic (analyzer chains) names
correspond too, as it is hardcoded somewhere deep with it.
> Make update processors toplevel components
> -------------------------------------------
>
> Key: SOLR-6892
> URL: https://issues.apache.org/jira/browse/SOLR-6892
> Project: Solr
> Issue Type: Bug
> Reporter: Noble Paul
> Assignee: Noble Paul
>
> The current update processor chain is rather cumbersome and we should be able
> to use the updateprocessors without a chain.
> The scope of this ticket is
> * <updateProcessor> tag becomes a toplevel tag and it will be equivalent to
> the <processor> tag inside <updateRequestProcessorChain> . The only
> difference is that it should require a {{name}} attribute
> * Any update request will be able to pass a param {{processor=a,b,c}} ,
> where a,b,c are names of update processors. A just in time chain will be
> created with those update processors
> * Some in built update processors (wherever possible) will be predefined with
> standard names and can be directly used in requests
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
