nifi-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mattyb149 <...@git.apache.org>
Subject [GitHub] nifi issue #1450: NIFI-3339b Add getDataSource() to DBCPService, second vers...
Date Tue, 07 Feb 2017 02:38:54 GMT
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.
---

Mime
View raw message