nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Rich <aaron.r...@gmail.com>
Subject Re: CM of nar via toolkit cli and regisry
Date Mon, 22 Jul 2019 03:59:17 GMT
Also,

When is 1.10.0 planned for release?

Thanks.

-Aaron


On Sun, Jul 21, 2019 at 9:29 PM Aaron Rich <aaron.rich@gmail.com> wrote:

> Great.
>
> Thank you.
>
> Is the best way to force my nar to use the 1.10 nifi-api via adding it as
> dependency is main pom file?
>
> Assuming I still need the build plugin also?
>
> Thanks again.
>
> -Aaron
>
> On Sun, Jul 21, 2019 at 9:30 AM Bryan Bende <bbende@gmail.com> wrote:
>
>> Hello,
>>
>> The issue is that in order to correctly generate the extension manifest
>> with the new NAR plugin, it requires changes from nifi-api that are not
>> released yet.
>>
>> You should be able to build NiFi on the master branch, really just the
>> nifi-api module, doing a mvn clean install.
>>
>> Then in your NAR you’ll need to force it to use 1.10.0-SNAPSHOT of
>> nifi-api. Currently you are getting 1.9.2 because of the parent of
>> nifi-nar-bundles.
>>
>> Once we get 1.10.0 released then this won’t be an issue anymore.
>>
>> Thanks,
>>
>> Bryan
>>
>> On Sat, Jul 20, 2019 at 11:36 PM Aaron Rich <aaron.rich@gmail.com> wrote:
>>
>> > I forgot to include that when generating the .nar, I do get the warnings
>> > of:
>> > [WARNING] Could not generate extensions' documentation
>> > org.apache.maven.plugin.MojoExecutionException: Failed to create
>> Extension
>> > Documentation
>> > ...
>> > Caused by: java.lang.NoSuchMethodException:
>> >
>> >
>> org.apache.nifi.documentation.xml.XmlDocumentationWriter.initialize(org.apache.nifi.components.ConfigurableComponent)
>> >
>> > I believe this is tied to not getting the right nfi-api version? But the
>> > parent is set to 1.9.2 so not sure how that is happening.
>> >
>> > Thanks again.
>> >
>> > -Aaron
>> >
>> > On Sat, Jul 20, 2019 at 9:09 PM Aaron Rich <aaron.rich@gmail.com>
>> wrote:
>> >
>> > > Hi,
>> > >
>> > > I'm trying to determine the best way to CM custom nar files for
>> sharing
>> > > between team. We are using nifi-registry for the flows and I saw there
>> > was
>> > > a new capability via the toolkit cli for "upload-bundle".
>> > >
>> > > I'm trying to use that but have ran into a few issues:
>> > > 1) I first wasn't getting the META-INF/docs/ in the .nar. I had built
>> the
>> > > initial project from mvn archetype:generate with version 1.9.2. I
>> added:
>> > > <build>
>> > > <plugins>
>> > > <plugin>
>> > > <groupId>org.apache.nifi</groupId>
>> > > <artifactId>nifi-nar-maven-plugin</artifactId>
>> > > <version>1.3.1</version>
>> > > <extensions>true</extensions>
>> > > </plugin>
>> > > </plugins>
>> > > </build>
>> > >
>> > > To the base pom.xml. It has the parent of:
>> > > <parent>
>> > > <groupId>org.apache.nifi</groupId>
>> > > <artifactId>nifi-nar-bundles</artifactId>
>> > > <version>1.9.2</version>
>> > > </parent>
>> > >
>> > > That got the docs in the jar:
>> > >      0 Sat Jul 20 20:53:44 MDT 2019 META-INF/docs/
>> > >     72 Sat Jul 20 20:53:44 MDT 2019
>> META-INF/docs/extension-manifest.xml
>> > >      0 Sat Jul 20 20:53:44 MDT 2019 META-INF/docs/additional-details/
>> > >
>> > > 2)I tried to use cli then with command:
>> > > ./bin/cli.sh registry upload-bundle --baseUrl http://localhost:18080/
>> > > --bucketId bcc0865e-818f-475b-b506-c95614b9a9d1 -ebt nifi-nar -ebf
>> > > .custom-processor-nar-1.0-SNAPSHOT.nar
>> > >
>> > > I get back "ERROR: Error executing command 'upload-bundle' : Error
>> > > creating extension bundle version: An unexpected error has occurred.
>> > Please
>> > > check the logs for additional details."
>> > >
>> > > In Registry log, error is:
>> > > Exception: Unable to obtain extension info for bundle due to: Unable
>> to
>> > > parse extension manifest due to: Unexpected end of input block;
>> expected
>> > an
>> > > identifier
>> > >  at [row,col {unknown-source}]: [1,72]
>> > >  at [Source:
>> > >
>> >
>> (org.apache.nifi.registry.bundle.extract.nar.NarBundleExtractor$NonCloseableInputStream);
>> > > line: 1, column: 73]. Returning Internal Server Error response.
>> > > org.apache.nifi.registry.bundle.extract.BundleException: Unable to
>> obtain
>> > > extension info for bundle due to: Unable to parse extension manifest
>> due
>> > > to: Unexpected end of input
>> > > block; expected an identifier
>> > >
>> > > Questions:
>> > > 1) Should I need to set the 1.3.1 plugin do get the docs in nar? I
>> > thought
>> > > that would be automatic from parent version being 1.9.2
>> > > 2) Is there an example for how to use the toolkit cli to
>> upload-bundle?
>> > > 3) Is there a better way to CM .nar? Archiva? Artifactory?
>> > >
>> > > Thanks.
>> > >
>> > > -Aaron
>> > >
>> > >
>> >
>> --
>> Sent from Gmail Mobile
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message