Putting this dependency in the root, with a version, worked. My
processor is loading.
Have you the time to tell me how building with this Maven dependency
forces the behavior I need? (Or what behavior this is?)
I thought that /nifi-dbcp-service-nar.nar/ was already loading before
when I
You’ll want to add a 1.12.0-SNAPSHOT (or a released version
of NiFi) before the ending tag
Sent from my iPhone
> On Jun 22, 2020, at 7:33 PM, Russell Bateman wrote:
>
> Thank you for replying. You speak of the following dependency:
>
> org.apache.nifi
> nifi-standard-services-api-nar
Thank you for replying. You speak of the following dependency:
org.apache.nifi
nifi-standard-services-api-nar
nar
I stumbled upon that, but could not make it work. My multimodule project
structure appears thus:
-root
- other submodules (whose custom processors work)
- jdbc
Not at my keyboard but does your NAR have the nifi-standard-services-api-nar as
a parent? That should be where DBCPService is defined
Sent from my iPhone
> On Jun 22, 2020, at 6:30 PM, Russell Bateman wrote:
>
> I find myself obliged to pick back up a custom processor, written by someone
>
I find myself obliged to pick back up a custom processor, written by
someone else a few years ago (in the NiFi 0.7.x era) at my company,
that makes use of DBCPService. While I think I understand the nuances of
interface versus concrete controller class, etc. I probably need a push
out the
Not that I'm aware of. All this so far just looks really easy to deal with.
On Mon, Jun 22, 2020 at 9:46 AM Mike Thomsen wrote:
> Out of curiosity... are there any cases you've found where we might have a
> term misalignment with what another product calls them? Like we might have
>
Out of curiosity... are there any cases you've found where we might have a
term misalignment with what another product calls them? Like we might have
primary/replica and the supported system uses master/slave?
On Mon, Jun 22, 2020 at 11:32 AM Joe Witt wrote:
> ...additional note after reviewing
...additional note after reviewing the presence of 'whitelist/blacklist' I
remain of the view what we need to do here is easy. There is minimal API
impact and it appears to be just the nifi.properties file for a property.
Other code changes do not appear to be API related and seem fair game now.
