Thanks very much Bryan, it works. đ The version of my customized processor
ends up coming from the version of my processor's pom.xml which is 1.0-SNAPSHOT
by default.
2017-05-22 21:06 GMT+08:00 Bryan Bende :
> I think the issue is that your NAR is probably including
> DBCPConnectionPool, rather t
I think the issue is that your NAR is probably including
DBCPConnectionPool, rather than depending on the API.
You could verify this by looking at the bundled dependencies in your
NAR
nifi_home/work/nar/extensions/-unpacked/META-INF/bundled-dependencies/,
you shouldn't have any DBCP related JARs
Sure, the content is as below:
Manifest-Version: 1.0
Build-Timestamp: 2017-05-19T14:45:05Z
Clone-During-Instance-Class-Loading: false
Archiver-Version: Plexus Archiver
Built-By: ben
Nar-Version: 3.0
Build-Tag: nifi-1.2.0-RC2
Nar-Id: nifi-DummyDataGeneratorProcessor-nar
Nar-Group: com.zjrealtech.rd
Can you provide the contents of the MANIFEST file of your NAR after
deploying your updated NAR?
The MANIFEST file should be at:
nifi_home/work/nar/extensions/-unpacked/META-INF/MANIFEST.MF
On Fri, May 19, 2017 at 3:16 AM, ĺ°šćć wrote:
> Hi Bryan, I could set a specific version for my customized p
Hi Bryan, I could set a specific version for my customized processor, but
there's a side effect that the version of NIFI components I referenced in
my processor are also updated to the same version.
I actually referenced DBCPService in my processor and I set the version to
a random version 3.0, and
Thanks Bryan and Joe, I managed to set the specific version for my
processor with the properties.
2017-05-18 20:50 GMT+08:00 Bryan Bende :
> As Joe mentioned, the default behavior is to use the Maven group,
> artifact, and version, which will happen by default if you build your
> NAR with the lat
As Joe mentioned, the default behavior is to use the Maven group,
artifact, and version, which will happen by default if you build your
NAR with the latest NAR Maven plugin (version 1.2.0 at this time).
If you prefer to set different values than the Maven fields, you can
override them by specifyin
Just rebuild it with the latest nifi nar maven plugin and it will get
the version info at that time.
thanks
On Thu, May 18, 2017 at 4:20 AM, ĺ°šćć wrote:
> Thanks Joe, is it possible to set a specific version for a customized NIFI
> processor and show the version in that processor selection dialog
Thanks Joe, is it possible to set a specific version for a customized NIFI
processor and show the version in that processor selection dialog?
2017-05-18 10:42 GMT+08:00 Joe Witt :
> Hello
>
> They will remain unversioned until they are built with the latest nar
> plugin. This is described briefl
Hello
They will remain unversioned until they are built with the latest nar
plugin. This is described briefly in the migration guidance [1].
For anything built with the older nifi nar plugin the resulting nar
will not have suffiicient bundle data for the framework to have it
support component ve
Hi guys, I have installed NIFI 1.2 and have played with it for a while.
One thing I noticed for 1.2 is that when I placed my previously written
customized Processor
into 1.2, I could see in the Processor select dialog there's a Version
field for each processor
and the value for my processor is unve
11 matches
Mail list logo
