lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (Commented) (JIRA) <>
Subject [jira] [Commented] (SOLR-2842) Re-factor UpdateChain and UpdateProcessor interfaces
Date Mon, 17 Oct 2011 11:18:10 GMT


Jan Høydahl commented on SOLR-2842:

Some valid points there. I thought I saw a possibility for generalization that would help
solve SOLR-1526, but wanted to flesh out the feasibility here.

So far I do not see any other example than Tika extraction which could really benefit from
being done client-side. There may be others, but perhaps not justifying this change.

Another option for SOLR-1526 could be to provide a ClientExtractingUpdateProcessorFactory
class which instantiates the ExtractingUpdateProcessor for client side use. Then if other
processors are useful on the client side as well, people simply write a Client factory for
> Re-factor UpdateChain and UpdateProcessor interfaces
> ----------------------------------------------------
>                 Key: SOLR-2842
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message