[
https://issues.apache.org/jira/browse/SOLR-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129030#comment-13129030
]
Ryan McKinley commented on SOLR-2842:
-------------------------------------
rather then use UpdateProcessor directly, what about adding a simple interface
like:
{code:java}
SolrInputDocument transform(SolrInputDocument)
{code}
and using simple bean getter/setters -- perhaps also respecting the 'aware'
interfaces (SolrCoreAware, SchemaAware, ResourceLoaderAware)
It seems like most of the custom things we would want to do only care about
'add' and don't care about commit,delete,merge,rollback. Starting with a
simple interface like this would give us lots of flexibility to integrate
wherever it feels most appropriate -- client/server or any other pipeline
framework (I've been using commons pipeline with pretty reasonable success)
> Re-factor UpdateChain and UpdateProcessor interfaces
> ----------------------------------------------------
>
> Key: SOLR-2842
> URL: https://issues.apache.org/jira/browse/SOLR-2842
> Project: Solr
> Issue Type: Improvement
> Components: update
> Reporter: Jan Høydahl
>
> The UpdateChain's main task is to send SolrInputDocuments through a chain of
> UpdateRequestProcessors in order to transform them in some way and then
> (typically) indexing them.
> This generic "pipeline" concept would also be useful on the client side
> (SolrJ), so that we could choose to do parts or all of the processing on the
> client. The most prominent use case is extracting text (Tika) from large
> binary documents, residing on local storage on the client(s). Streaming
> hundreds of Mb over to Solr for processing is not efficcient. See SOLR-1526.
> We're already implementing Tika as an UpdateProcessor in SOLR-1763, and what
> would be more natural than reusing this - and any other processor - on the
> client side?
> However, for this to be possible, some interfaces need to change slightly..
--
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]
