Return-Path: X-Original-To: apmail-manifoldcf-dev-archive@www.apache.org Delivered-To: apmail-manifoldcf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4A5851026D for ; Wed, 11 Jun 2014 16:29:02 +0000 (UTC) Received: (qmail 60636 invoked by uid 500); 11 Jun 2014 16:29:02 -0000 Delivered-To: apmail-manifoldcf-dev-archive@manifoldcf.apache.org Received: (qmail 60584 invoked by uid 500); 11 Jun 2014 16:29:01 -0000 Mailing-List: contact dev-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@manifoldcf.apache.org Delivered-To: mailing list dev@manifoldcf.apache.org Received: (qmail 60574 invoked by uid 99); 11 Jun 2014 16:29:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jun 2014 16:29:01 +0000 Date: Wed, 11 Jun 2014 16:29:01 +0000 (UTC) From: "Karl Wright (JIRA)" To: dev@manifoldcf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CONNECTORS-962) Support multiple output connections for a single job MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Karl Wright created CONNECTORS-962: -------------------------------------- Summary: Support multiple output connections for a single job Key: CONNECTORS-962 URL: https://issues.apache.org/jira/browse/CONNECTORS-962 Project: ManifoldCF Issue Type: Improvement Components: Framework crawler agent Affects Versions: ManifoldCF 1.7 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 1.7 Zaizi has a requirement to support multiple outputs for a single job. In theory this requirement can be met by doing the following: - Allow multiple output connections, and multiple pipelines, per job - Keep a distinct ingeststatus record for each document/output combination - Modify WorkerThread to call IncrementalIndexer multiple times for every document fetched Places where different things need to happen are: - RepositoryDocument - because one binary stream will not do for multiple outputs - UI, obviously, because there will need to be multiple pipelines, not just one, and in addition it would be probably important to be able to "split" the pipeline at arbitrary points -- This message was sent by Atlassian JIRA (v6.2#6252)