From users-return-6076-apmail-nifi-users-archive=nifi.apache.org@nifi.apache.org Sun Jun 11 20:07:09 2017 Return-Path: X-Original-To: apmail-nifi-users-archive@minotaur.apache.org Delivered-To: apmail-nifi-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9504D1A60A for ; Sun, 11 Jun 2017 20:07:09 +0000 (UTC) Received: (qmail 63865 invoked by uid 500); 11 Jun 2017 20:07:09 -0000 Delivered-To: apmail-nifi-users-archive@nifi.apache.org Received: (qmail 63813 invoked by uid 500); 11 Jun 2017 20:07:09 -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 63803 invoked by uid 99); 11 Jun 2017 20:07:09 -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, 11 Jun 2017 20:07:09 +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 E719E1A052D for ; Sun, 11 Jun 2017 20:07:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1 X-Spam-Level: * X-Spam-Status: No, score=1 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id 20WY4wRbJwpc for ; Sun, 11 Jun 2017 20:07:08 +0000 (UTC) Received: from secure.my2ndhead.com (static.183.104.4.46.clients.your-server.de [46.4.104.183]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 91A545F30B for ; Sun, 11 Jun 2017 20:07:07 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by secure.my2ndhead.com (Postfix) with ESMTP id 0BCA722800B1 for ; Sun, 11 Jun 2017 22:07:01 +0200 (CEST) Received: from secure.my2ndhead.com ([127.0.0.1]) by localhost (secure.my2ndhead.com [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id a6nuqV2g7tpu for ; Sun, 11 Jun 2017 22:07:00 +0200 (CEST) Received: from localhost (localhost.localdomain [127.0.0.1]) by secure.my2ndhead.com (Postfix) with ESMTP id E7ED822800A8 for ; Sun, 11 Jun 2017 22:06:59 +0200 (CEST) X-Virus-Scanned: amavisd-new at my2ndhead.com Received: from secure.my2ndhead.com ([127.0.0.1]) by localhost (secure.my2ndhead.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id XG-GSMptyhcF for ; Sun, 11 Jun 2017 22:06:59 +0200 (CEST) Received: from [192.168.178.100] (212-51-128-150.fiber7.init7.net [212.51.128.150]) by secure.my2ndhead.com (Postfix) with ESMTPSA id BECAD22800A7 for ; Sun, 11 Jun 2017 22:06:59 +0200 (CEST) From: Mika Borner Subject: Questions about record processors To: users@nifi.apache.org Message-ID: Date: Sun, 11 Jun 2017 22:06:59 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US Hi Been playing with the new record processors (great so far!). Now I have two questions about usage. 1. Let's say I have an Update Record processor with a GrokReader and a JsonRecordSetWriter manipulating the record. This works fine. Now I want to further process the records with a LookupRecord and/or a QueryRecord processor. In my case, setting the Record Reader for chained record processors to JsonTreeReader seems to work. Just wondering if this is the right thing to do, as there are only examples with a single record processor. 2. I haven't figured out yet, how the LookupRecord processor configuration has to be done. My lookup table contains two columns and one row foo, bar foovalue1, barvalue1 The SimpleCsvFileLookupService has "Lookup Key Column" set to "foo" and "Lookup Value Column" to "bar". The LookupRecord processor has "Result RecordPath" set to //bar. The property "key" is set to //foo. Here I'm not sure if the property name "key" is correct. Any other value causes an error. Unfortunately the lookup doesn't work and I also couldn't find any examples in the documentation. Thanks for your help! Mika>