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 32481200C2D for ; Sat, 18 Feb 2017 03:53:26 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 30C6D160B6D; Sat, 18 Feb 2017 02:53: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 7B71D160B57 for ; Sat, 18 Feb 2017 03:53:25 +0100 (CET) Received: (qmail 97261 invoked by uid 500); 18 Feb 2017 02:53:24 -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 97250 invoked by uid 99); 18 Feb 2017 02:53:24 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Feb 2017 02:53:24 +0000 Received: from mail-qk0-f175.google.com (mail-qk0-f175.google.com [209.85.220.175]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 3DCC81A02C9 for ; Sat, 18 Feb 2017 02:53:24 +0000 (UTC) Received: by mail-qk0-f175.google.com with SMTP id u25so59729134qki.2 for ; Fri, 17 Feb 2017 18:53:24 -0800 (PST) X-Gm-Message-State: AMke39kRBMxHWmDynLgD53f49Ql+L/XpOApuc9IUKsDvqPJzCQ1uvySmmqzCKVkUo6gX6LmywfVvtqp6RbpRzw== X-Received: by 10.55.114.132 with SMTP id n126mr10389062qkc.112.1487386403434; Fri, 17 Feb 2017 18:53:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.165.99 with HTTP; Fri, 17 Feb 2017 18:53:23 -0800 (PST) In-Reply-To: <11011351487325939@web17h.yandex.ru> References: <11011351487325939@web17h.yandex.ru> From: Matt Burgess Date: Fri, 17 Feb 2017 21:53:23 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Creating a custom DatabaseAdapter To: dev@nifi.apache.org Content-Type: text/plain; charset=UTF-8 archived-at: Sat, 18 Feb 2017 02:53:26 -0000 Stanislav, This is not your fault, it is a current limitation due to the organization of the NiFi submodules with respect to the location of DatabaseAdapter. In general, when a NiFi interface is to be extensible, there is a submodule for the API JAR to be available to other NARs/submodules/etc. In this case, we'd likely want DatabaseAdapter (and any related classes) to be included in nifi-standard-services-api-nar as its own API NAR, yet at the moment it is a class inside nifi-standard-nar. I agree that we should make this interface available, and refactor the submodules accordingly to make DatabaseAdapter extensible outside the nifi-standard NAR. Some care should be given to which "parent NAR" it belongs, in order to ensure that we don't upset the current mechanism of one parent NAR per child NAR, but hopefully "nifi-services-api-nar" is the right spot. Do you mind writing up a Jira case for this? I think it will help the community in general as various DB integrations are desired. Thanks in advance, Matt On Fri, Feb 17, 2017 at 5:05 AM, Stanislav wrote: > Hi, > > I would like to create a custom org.apache.nifi.processors.standard.db.DatabaseAdapter, is this possible? > I have tried creating new class that implements the interface and specified the full class name in META-INF\services\org.apache.nifi.processors.standard.db.DatabaseAdapter file, and created a nar. > But this does not appear to be working, the custom processor i have in that nar are picked-up but the DatabaseAdapter isn`t. > Any tips on how to make it work? > > Best regards, > Stanislav.