Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 90EC2200B28 for ; Sun, 26 Jun 2016 14:40:58 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 84590160A5C; Sun, 26 Jun 2016 12:40:58 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id F18AD160A28 for ; Sun, 26 Jun 2016 14:40:57 +0200 (CEST) Received: (qmail 46085 invoked by uid 500); 26 Jun 2016 12:40:56 -0000 Mailing-List: contact dev-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list dev@nifi.apache.org Received: (qmail 46067 invoked by uid 99); 26 Jun 2016 12:40:54 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Jun 2016 12:40:54 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id ACFFB1A5E44 for ; Sun, 26 Jun 2016 12:40:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id q6qZ-aOVPuWU for ; Sun, 26 Jun 2016 12:40:50 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 05A4E5F29B for ; Sun, 26 Jun 2016 12:40:49 +0000 (UTC) Received: from mtom.nabble.com (unknown [162.253.133.81]) by mbob.nabble.com (Postfix) with ESMTP id 5F02F2B2D14D for ; Sun, 26 Jun 2016 05:19:59 -0700 (PDT) Date: Sun, 26 Jun 2016 04:30:57 -0700 (MST) From: ddewaele To: dev@nifi.apache.org Message-ID: <1466940657854-12278.post@n7.nabble.com> Subject: ListS3 processor question (duplicate files / maintaining state) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit archived-at: Sun, 26 Jun 2016 12:40:58 -0000 Hi, I had a question on the ListS3 processor. I'm using it to monitor the content of an S3 bucket. The idea is that when new files come in, they need to be processed and sent through the dataflow, using a FetchS3Object to process the file. This all works but I had 2 questions : 1. Where does the S3 processor keep its state ? How does it know what files it has already processed and is there a way to clear this state ? 2. Sometimes, when syncing files to my S3 buckets, I notice that the ListS3 processor is picking up the same file twice. Is there a way to avoid that ? -- View this message in context: http://apache-nifi-developer-list.39713.n7.nabble.com/ListS3-processor-question-duplicate-files-maintaining-state-tp12278.html Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.