Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Mon, 17 Oct 2011 19:41:10 +0000 (UTC)
From: =?utf-8?Q?Jan_H=C3=B8ydahl_=28Commented=29_=28JIRA=29?=
 <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <412198079.1696.1318880470782.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1305302746.18333.1318772051937.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (SOLR-2842) Re-factor UpdateChain and
 UpdateProcessor interfaces
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/SOLR-2842?page=3Dcom.atlassian.=
jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13129=
112#comment-13129112 ]=20

Jan H=C3=B8ydahl commented on SOLR-2842:
-----------------------------------

Interesting thought Ryan. I already commonly isolate processing in a simila=
r method to simplify unit testing so this is useful in several ways. Do you=
 suggest to let UpdateProcessor base class implement this interface? But yo=
u still need to construct and initialize the processors even if they are wr=
apped in the interface, thus my suggestion for a client side version of the=
 factory.
               =20
> 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=C3=B8ydahl
>
> 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 b=
inary documents, residing on local storage on the client(s). Streaming hund=
reds 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 w=
hat 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 administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org