From issues-return-19325-apmail-nifi-issues-archive=nifi.apache.org@nifi.apache.org Tue Feb 7 02:38:54 2017 Return-Path: X-Original-To: apmail-nifi-issues-archive@minotaur.apache.org Delivered-To: apmail-nifi-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5831D197DB for ; Tue, 7 Feb 2017 02:38:54 +0000 (UTC) Received: (qmail 15137 invoked by uid 500); 7 Feb 2017 02:38:54 -0000 Delivered-To: apmail-nifi-issues-archive@nifi.apache.org Received: (qmail 15106 invoked by uid 500); 7 Feb 2017 02:38:54 -0000 Mailing-List: contact issues-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 issues@nifi.apache.org Received: (qmail 15097 invoked by uid 99); 7 Feb 2017 02:38:54 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Feb 2017 02:38:54 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 1854BDFC15; Tue, 7 Feb 2017 02:38:54 +0000 (UTC) From: mattyb149 To: issues@nifi.apache.org Reply-To: issues@nifi.apache.org References: In-Reply-To: Subject: [GitHub] nifi issue #1450: NIFI-3339b Add getDataSource() to DBCPService, second vers... Content-Type: text/plain Message-Id: <20170207023854.1854BDFC15@git1-us-west.apache.org> Date: Tue, 7 Feb 2017 02:38:54 +0000 (UTC) Github user mattyb149 commented on the issue: https://github.com/apache/nifi/pull/1450 My use case is a third-party library that takes the same information you might put into a DBCPControllerService, either in the URL and/or the username/password, etc. I was hoping to avoid trying to parse the URL looking for some properties (hostname:port) and need access to other properties (username/password). I could just add these properties explicitly to my processor(s), especially if there'd be a lot of refactor involved with making such information available via DBCPService. Your getTransitUri() addition would be a good improvement IMO, I added something similar to HiveDBCPService (a getConnectionURL() method). If we added that to DBCPService we could remove it from HiveDBCPService (although I would still keep the class as a marker interface). I withdraw my use case from this discussion as I can accomplish it another way, and as the processor(s) I am working on are TriggerSerially and to be run on the Primary Node only, I doubt there's much to be gained by reusing a Controller Service anyway. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastructure@apache.org or file a JIRA ticket with INFRA. ---