From users-return-7755-archive-asf-public=cust-asf.ponee.io@nifi.apache.org Thu Jan 4 16:12:18 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id E8CB2180657 for ; Thu, 4 Jan 2018 16:12:18 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id D8964160C2B; Thu, 4 Jan 2018 15:12:18 +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 29FC2160C28 for ; Thu, 4 Jan 2018 16:12:18 +0100 (CET) Received: (qmail 87499 invoked by uid 500); 4 Jan 2018 15:12:17 -0000 Mailing-List: contact users-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@nifi.apache.org Delivered-To: mailing list users@nifi.apache.org Received: (qmail 87489 invoked by uid 99); 4 Jan 2018 15:12:17 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jan 2018 15:12:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 77B9EC07A9 for ; Thu, 4 Jan 2018 15:12:16 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.129 X-Spam-Level: ** X-Spam-Status: No, score=2.129 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id oddlNXGY9iJt for ; Thu, 4 Jan 2018 15:12:15 +0000 (UTC) Received: from mail-vk0-f54.google.com (mail-vk0-f54.google.com [209.85.213.54]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 8E9A95F1B9 for ; Thu, 4 Jan 2018 15:12:15 +0000 (UTC) Received: by mail-vk0-f54.google.com with SMTP id m15so1086023vkf.13 for ; Thu, 04 Jan 2018 07:12:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=S3Loq3kv79JX948r2tkrrRP1+awketI2lG9UShruO/A=; b=bKVXAVogm0JzOBUpF89huirHOZ+qogX4tS0p00xEo6ocFk4ve18ANjmupF1ILhcrUc qrhslA3QPf1GwGiyEI03WVdJSZq/kekPzMIU4nau11ZlnkjPYi/HIEmoio1+vzl38+1W qH6Ykrmg9LkBN4XcRhpn+r4ZUpz1uA1A+REoLAjHArTHrDpoGHPULmIJRmmoKufus8ZT /0chavRltHLWSwMBWdx4Gs/KcoNnwvVxkqSn9R4omN4efxw50F8z9CMecmzGZG4k20Iq gDv++bC3DwjseE+9TLvkAnXKWY9CI//mBZGidHFGFdc1ZPcwrS589L0d1bIQjt3aIGiZ 3idA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=S3Loq3kv79JX948r2tkrrRP1+awketI2lG9UShruO/A=; b=KKhJYoW9qcr7JaM3Ng/CXyF/KGQJit5CtIobmAG0auC4WXZWOfVpTr1rept3Xfxdtd 7fc4Wny/YrOP+/p1ArhAEwiS1W7nAR0FWhZ9URSJVlbnGgHHfw+WQT57RhTPFFXVpVh9 +7xGh7FzfzJ3mULHjYSnZFZPOgbwAhRDDzHVUqvb53AEgBwwkLPlZoTLPMQNiV825eDT 7XD+bxYxvu5cFEmmlJtXrPxbQuTQ9SRkGrlp6NoSl8df15lJa5CTjowHoN9fffy44jtM 0Ah9rKXMtg9uodkWPVdKMvQNzqw2FP91n5p0A8K4FmpCpOhDQmi0RBvpyOJrKh1pmPtd KYXQ== X-Gm-Message-State: AKGB3mJpgeaWwbg4I72LnSs4sdl3/m40hEpIVfylTiSWFAxvrehlz73b l1Fetz3c/WHnxTiIJsySeoWhkJh0KTbuFnsXgUw= X-Google-Smtp-Source: ACJfBotK3qkxt6OrzNHaOWpd3+hXRTRD/XJwzUh7kDNfV47q9tc5wuXuAm8J2sifUgzdJIE0Bynli4vS4KJCqA2PVfc= X-Received: by 10.31.226.132 with SMTP id z126mr4684380vkg.89.1515078734879; Thu, 04 Jan 2018 07:12:14 -0800 (PST) MIME-Version: 1.0 Received: by 10.103.103.198 with HTTP; Thu, 4 Jan 2018 07:12:14 -0800 (PST) From: Martin Mucha Date: Thu, 4 Jan 2018 16:12:14 +0100 Message-ID: Subject: Get the failure reason from ValidateResult processor To: users@nifi.apache.org Content-Type: multipart/alternative; boundary="001a114da64ccca23b0561f4c143" --001a114da64ccca23b0561f4c143 Content-Type: text/plain; charset="UTF-8" Hi, I'm having difficulties to find a way how to get the failure reason from ValidateResult processor. I know, it emits the route provenance event, but you cannot integrate that in your flow as far as I know. I also saw suggestion to write custom reporting task, but a) that one does not have access to original FlowFile and generally it does not seem to be sound solution. On the otherhand ConvertToAvro validator creates new `Details` attribute to describe failure. (well at least it used to do so? I cannot find that Details property in documentation any more). am I overlooking something? What I'd like to do, is to work with failure reason further in flow, where I get along `invalid` relationship. Thanks for advice. Martin. --001a114da64ccca23b0561f4c143 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I'm having difficulties to find= a way how to get the failure reason from ValidateResult processor. I know,= it emits the route provenance event, but you cannot integrate that in your= flow as far as I know. I also saw suggestion to write custom reporting tas= k, but a) that one does not have access to original FlowFile and generally = it does not seem to be sound solution.=C2=A0

On th= e otherhand ConvertToAvro validator creates new `Details` attribute to desc= ribe failure. (well at least it used to do so? I cannot find that Details p= roperty in documentation any more).

am I overlooki= ng something? What I'd like to do, is to work with failure reason furth= er in flow, where I get along `invalid` relationship.

<= div>Thanks for advice.

Martin.
--001a114da64ccca23b0561f4c143--