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 C7BED200B78 for ; Fri, 2 Sep 2016 23:47:26 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C64F9160AAE; Fri, 2 Sep 2016 21:47:26 +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 1A6A4160A8C for ; Fri, 2 Sep 2016 23:47:25 +0200 (CEST) Received: (qmail 17227 invoked by uid 500); 2 Sep 2016 21:47:25 -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 17215 invoked by uid 99); 2 Sep 2016 21:47:25 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2016 21:47:25 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id C4B52188590 for ; Fri, 2 Sep 2016 21:47:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.573 X-Spam-Level: X-Spam-Status: No, score=0.573 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id oRLmQTTEROT6 for ; Fri, 2 Sep 2016 21:47:23 +0000 (UTC) Received: from mx9.sapient.com (mx9.sapient.com [12.130.39.183]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 1AFFE5F24D for ; Fri, 2 Sep 2016 21:47:23 +0000 (UTC) Received: from unknown (HELO mx9.sapient.com) ([10.207.74.35]) by MX9int.sapient.com with ESMTP; 02 Sep 2016 17:47:15 -0400 Received: from DLUMAIL02.sapient.com ([fe80::2d3e:7873:aa7:18a8]) by DLUHUB01.sapient.com ([::1]) with mapi id 14.03.0210.002; Sat, 3 Sep 2016 03:17:14 +0530 From: Manish Gupta 8 To: "users@nifi.apache.org" Subject: Processor to enrich attribute from external service Thread-Topic: Processor to enrich attribute from external service Thread-Index: AdIFY3L9rY+5xmckSvG/myw/OPnucA== Date: Fri, 2 Sep 2016 21:47:13 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.57.132] Content-Type: multipart/alternative; boundary="_000_C323735DFA07DC4BBB568EC328CBC54331C8DBD4DLUMAIL02sapien_" MIME-Version: 1.0 archived-at: Fri, 02 Sep 2016 21:47:27 -0000 --_000_C323735DFA07DC4BBB568EC328CBC54331C8DBD4DLUMAIL02sapien_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Everyone, Is there a processor that we can use for updating/adding an attribute of an= incoming flow file from some external service (say MongoDB or Couchbase or= any RDBMS)? The processor will use the attribute of incoming flow file, qu= ery the external service, and simply modify/add an additional attribute of = flow-file (without touching the flow file content). If we have to achieve this kind of "lookup" operation (but only to update a= ttribute and not the content), what are the options in NiFi? Should we create a custom processor (may be by taking GetMongo processor an= d modifying its code to update an attribute with query result)? Thanks, Manish --_000_C323735DFA07DC4BBB568EC328CBC54331C8DBD4DLUMAIL02sapien_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello Everyone,

 

Is there a processor that we can use for updating/ad= ding an attribute of an incoming flow file from some external service (say = MongoDB or Couchbase or any RDBMS)? The processor will use the attribute of= incoming flow file, query the external service, and simply modify/add an additional attribute of flow-file (witho= ut touching the flow file content).

 

If we have to achieve this kind of “lookupR= 21; operation (but only to update attribute and not the content), what are = the options in NiFi?

Should we create a custom processor (may be by takin= g GetMongo processor and modifying its code to update an attribute with que= ry result)?

 

Thanks,

Manish=

 

--_000_C323735DFA07DC4BBB568EC328CBC54331C8DBD4DLUMAIL02sapien_--