[jira] [Assigned] (NIFI-11368) Make docker and docker-maven modules consistent and more consolidated
[ https://issues.apache.org/jira/browse/NIFI-11368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran reassigned NIFI-11368: -- Assignee: Kevin Doran > Make docker and docker-maven modules consistent and more consolidated > - > > Key: NIFI-11368 > URL: https://issues.apache.org/jira/browse/NIFI-11368 > Project: Apache NiFi > Issue Type: Improvement > Components: Docker >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Major > Fix For: 2.latest > > > Currently, the docker and docker-maven modules across the NiFi repository > lack consistency and can be farther consolidated to avoid duplication. > This ticket is to see how we can build on recent improvements to docker image > building and project structure to drive even more consistency and code reuse > across docker and docker maven for all the images in the nifi repo: nifi, > nifi-registry, nifi-toolkit, nifi-minifi, nifi-minifi-c2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11368) Make docker and docker-maven modules consistent and more consolidated
[ https://issues.apache.org/jira/browse/NIFI-11368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-11368: --- Description: Currently, the docker and docker-maven modules across the NiFi repository lack consistency and can be farther consolidated to avoid duplication. This ticket is to see how we can build on recent improvements to docker image building and project structure to drive even more consistency and code reuse across docker and docker maven for all the images in the nifi repo: nifi, nifi-registry, nifi-toolkit, nifi-minifi, nifi-minifi-c2 was: Currently, the docker and docker-maven modules across the NiFi repository lake consistency and can be farther consolidated to avoid duplication. This ticket is to see how we can build on recent improvements to docker image building and project structure to drive even more consistency and code reuse across docker and docker maven for all the images in the nifi repo: nifi, nifi-registry, nifi-toolkit, nifi-minifi, nifi-minifi-c2 > Make docker and docker-maven modules consistent and more consolidated > - > > Key: NIFI-11368 > URL: https://issues.apache.org/jira/browse/NIFI-11368 > Project: Apache NiFi > Issue Type: Improvement > Components: Docker >Reporter: Kevin Doran >Priority: Major > Fix For: 2.latest > > > Currently, the docker and docker-maven modules across the NiFi repository > lack consistency and can be farther consolidated to avoid duplication. > This ticket is to see how we can build on recent improvements to docker image > building and project structure to drive even more consistency and code reuse > across docker and docker maven for all the images in the nifi repo: nifi, > nifi-registry, nifi-toolkit, nifi-minifi, nifi-minifi-c2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11368) Make docker and docker-maven modules consistent and more consolidated
Kevin Doran created NIFI-11368: -- Summary: Make docker and docker-maven modules consistent and more consolidated Key: NIFI-11368 URL: https://issues.apache.org/jira/browse/NIFI-11368 Project: Apache NiFi Issue Type: Improvement Components: Docker Reporter: Kevin Doran Fix For: 2.latest Currently, the docker and docker-maven modules across the NiFi repository lake consistency and can be farther consolidated to avoid duplication. This ticket is to see how we can build on recent improvements to docker image building and project structure to drive even more consistency and code reuse across docker and docker maven for all the images in the nifi repo: nifi, nifi-registry, nifi-toolkit, nifi-minifi, nifi-minifi-c2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11351) Support dockermaven build on aarch64/arm64 platforms
[ https://issues.apache.org/jira/browse/NIFI-11351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-11351: --- Fix Version/s: 2.latest > Support dockermaven build on aarch64/arm64 platforms > > > Key: NIFI-11351 > URL: https://issues.apache.org/jira/browse/NIFI-11351 > Project: Apache NiFi > Issue Type: Sub-task > Components: Tools and Build >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Minor > Fix For: 2.latest > > > Our current docker maven plugin only runs on x86_64 architectures and is no > longer actively maintained. This ticket is to switch to a replacement. This > one looks promising: > https://springframework.guru/fabric8-docker-maven-plugin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10017) TLS-Toolkit standalone gives "Java heap space" error
[
https://issues.apache.org/jira/browse/NIFI-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17706618#comment-17706618
]
Kevin Doran commented on NIFI-10017:
Thanks for reporting [~daniel.salwerowicz]. Spot on with your analysis. Change
submitted here:
https://github.com/apache/nifi/pull/7100
> TLS-Toolkit standalone gives "Java heap space" error
>
>
> Key: NIFI-10017
> URL: https://issues.apache.org/jira/browse/NIFI-10017
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management, Tools and Build
>Affects Versions: 1.16.1, 1.20.0
> Environment: CentOS server, Java 11
>Reporter: Daniel Salwerowicz
>Assignee: Kevin Doran
>Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When I invoked tls-toolkit during installation of a new (1.16.1) NiFi
> instance on server I got following error from toolkit.
> {noformat}
> nifi-toolkit-1.16.1/bin/tls-toolkit.sh standalone \
> -C "..." \
> -K "..." \
> -S "..." \
> -P "..." \
> -f "/disk1/nifi/prod/nifi-1.16.1/conf/nifi.properties" \
> -o ./certificate \
> -n "..." \
> -O
> [main] INFO
> org.apache.nifi.toolkit.tls.standalone.TlsToolkitStandaloneCommandLine -
> Using /disk1/nifi/prod/nifi-1.16.1/conf/nifi.properties as template.
> Service standalone error: Java heap space{noformat}
> Upon reading the script I noticed a small problem on line 114 of the
> "tls-toolkit.sh" file:
> {noformat}
> exec "${JAVA}" -cp "${CLASSPATH}" ${JAVA_OPTS:--Xms12m -Xmx24m}
> org.apache.nifi.toolkit.tls.TlsToolkitMain "$@"
> {noformat}
> If you look at the {{JAVA_OPTS}} it assigns only 12 and 24 Mb as min and max
> heap size available to the java process it executes. I think this causes the
> java process to run out of heap space, when I increased it to 128 and 256 Mb
> like in "encrypt-config.sh" then it worked alright.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-10017) TLS-Toolkit standalone gives "Java heap space" error
[
https://issues.apache.org/jira/browse/NIFI-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-10017:
---
Affects Version/s: 1.20.0
Status: Patch Available (was: In Progress)
> TLS-Toolkit standalone gives "Java heap space" error
>
>
> Key: NIFI-10017
> URL: https://issues.apache.org/jira/browse/NIFI-10017
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management, Tools and Build
>Affects Versions: 1.20.0, 1.16.1
> Environment: CentOS server, Java 11
>Reporter: Daniel Salwerowicz
>Assignee: Kevin Doran
>Priority: Major
> Fix For: 1.latest, 2.latest
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When I invoked tls-toolkit during installation of a new (1.16.1) NiFi
> instance on server I got following error from toolkit.
> {noformat}
> nifi-toolkit-1.16.1/bin/tls-toolkit.sh standalone \
> -C "..." \
> -K "..." \
> -S "..." \
> -P "..." \
> -f "/disk1/nifi/prod/nifi-1.16.1/conf/nifi.properties" \
> -o ./certificate \
> -n "..." \
> -O
> [main] INFO
> org.apache.nifi.toolkit.tls.standalone.TlsToolkitStandaloneCommandLine -
> Using /disk1/nifi/prod/nifi-1.16.1/conf/nifi.properties as template.
> Service standalone error: Java heap space{noformat}
> Upon reading the script I noticed a small problem on line 114 of the
> "tls-toolkit.sh" file:
> {noformat}
> exec "${JAVA}" -cp "${CLASSPATH}" ${JAVA_OPTS:--Xms12m -Xmx24m}
> org.apache.nifi.toolkit.tls.TlsToolkitMain "$@"
> {noformat}
> If you look at the {{JAVA_OPTS}} it assigns only 12 and 24 Mb as min and max
> heap size available to the java process it executes. I think this causes the
> java process to run out of heap space, when I increased it to 128 and 256 Mb
> like in "encrypt-config.sh" then it worked alright.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-10017) TLS-Toolkit standalone gives "Java heap space" error
[
https://issues.apache.org/jira/browse/NIFI-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-10017:
---
Fix Version/s: 1.latest
2.latest
> TLS-Toolkit standalone gives "Java heap space" error
>
>
> Key: NIFI-10017
> URL: https://issues.apache.org/jira/browse/NIFI-10017
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management, Tools and Build
>Affects Versions: 1.16.1
> Environment: CentOS server, Java 11
>Reporter: Daniel Salwerowicz
>Assignee: Kevin Doran
>Priority: Major
> Fix For: 1.latest, 2.latest
>
>
> When I invoked tls-toolkit during installation of a new (1.16.1) NiFi
> instance on server I got following error from toolkit.
> {noformat}
> nifi-toolkit-1.16.1/bin/tls-toolkit.sh standalone \
> -C "..." \
> -K "..." \
> -S "..." \
> -P "..." \
> -f "/disk1/nifi/prod/nifi-1.16.1/conf/nifi.properties" \
> -o ./certificate \
> -n "..." \
> -O
> [main] INFO
> org.apache.nifi.toolkit.tls.standalone.TlsToolkitStandaloneCommandLine -
> Using /disk1/nifi/prod/nifi-1.16.1/conf/nifi.properties as template.
> Service standalone error: Java heap space{noformat}
> Upon reading the script I noticed a small problem on line 114 of the
> "tls-toolkit.sh" file:
> {noformat}
> exec "${JAVA}" -cp "${CLASSPATH}" ${JAVA_OPTS:--Xms12m -Xmx24m}
> org.apache.nifi.toolkit.tls.TlsToolkitMain "$@"
> {noformat}
> If you look at the {{JAVA_OPTS}} it assigns only 12 and 24 Mb as min and max
> heap size available to the java process it executes. I think this causes the
> java process to run out of heap space, when I increased it to 128 and 256 Mb
> like in "encrypt-config.sh" then it worked alright.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (NIFI-10017) TLS-Toolkit standalone gives "Java heap space" error
[
https://issues.apache.org/jira/browse/NIFI-10017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran reassigned NIFI-10017:
--
Assignee: Kevin Doran
> TLS-Toolkit standalone gives "Java heap space" error
>
>
> Key: NIFI-10017
> URL: https://issues.apache.org/jira/browse/NIFI-10017
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration Management, Tools and Build
>Affects Versions: 1.16.1
> Environment: CentOS server, Java 11
>Reporter: Daniel Salwerowicz
>Assignee: Kevin Doran
>Priority: Major
>
> When I invoked tls-toolkit during installation of a new (1.16.1) NiFi
> instance on server I got following error from toolkit.
> {noformat}
> nifi-toolkit-1.16.1/bin/tls-toolkit.sh standalone \
> -C "..." \
> -K "..." \
> -S "..." \
> -P "..." \
> -f "/disk1/nifi/prod/nifi-1.16.1/conf/nifi.properties" \
> -o ./certificate \
> -n "..." \
> -O
> [main] INFO
> org.apache.nifi.toolkit.tls.standalone.TlsToolkitStandaloneCommandLine -
> Using /disk1/nifi/prod/nifi-1.16.1/conf/nifi.properties as template.
> Service standalone error: Java heap space{noformat}
> Upon reading the script I noticed a small problem on line 114 of the
> "tls-toolkit.sh" file:
> {noformat}
> exec "${JAVA}" -cp "${CLASSPATH}" ${JAVA_OPTS:--Xms12m -Xmx24m}
> org.apache.nifi.toolkit.tls.TlsToolkitMain "$@"
> {noformat}
> If you look at the {{JAVA_OPTS}} it assigns only 12 and 24 Mb as min and max
> heap size available to the java process it executes. I think this causes the
> java process to run out of heap space, when I increased it to 128 and 256 Mb
> like in "encrypt-config.sh" then it worked alright.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-11351) Support dockermaven build on aarch64/arm64 platforms
Kevin Doran created NIFI-11351: -- Summary: Support dockermaven build on aarch64/arm64 platforms Key: NIFI-11351 URL: https://issues.apache.org/jira/browse/NIFI-11351 Project: Apache NiFi Issue Type: Sub-task Components: Tools and Build Reporter: Kevin Doran Assignee: Kevin Doran Our current docker maven plugin only runs on x86_64 architectures and is no longer actively maintained. This ticket is to switch to a replacement. This one looks promising: https://springframework.guru/fabric8-docker-maven-plugin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11283) Add GitHub Actions CI build to nifi-maven project
[ https://issues.apache.org/jira/browse/NIFI-11283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-11283: --- Fix Version/s: nifi-nar-maven-plugin-1.5.1 > Add GitHub Actions CI build to nifi-maven project > - > > Key: NIFI-11283 > URL: https://issues.apache.org/jira/browse/NIFI-11283 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Kevin Doran >Assignee: David Handermann >Priority: Major > Fix For: nifi-nar-maven-plugin-1.5.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > > We should have CI builds with contrib-check for the NAR Maven Plugin repo. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-11278) Release Manager - Release NAR Maven Plugin 1.5.0
[ https://issues.apache.org/jira/browse/NIFI-11278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran resolved NIFI-11278. Resolution: Done > Release Manager - Release NAR Maven Plugin 1.5.0 > > > Key: NIFI-11278 > URL: https://issues.apache.org/jira/browse/NIFI-11278 > Project: Apache NiFi > Issue Type: Task > Components: Tools and Build >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Major > Fix For: nifi-nar-maven-plugin-1.5.0 > > > Release Manager activities related to releasing NAR Maven Plugin 1.5.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11283) Add GitHub Actions CI build to nifi-maven project
Kevin Doran created NIFI-11283: -- Summary: Add GitHub Actions CI build to nifi-maven project Key: NIFI-11283 URL: https://issues.apache.org/jira/browse/NIFI-11283 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Kevin Doran We should have CI builds with contrib-check for the NAR Maven Plugin repo. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11282) Fix checkstyle failures in NAR Maven Plugin
Kevin Doran created NIFI-11282:
--
Summary: Fix checkstyle failures in NAR Maven Plugin
Key: NIFI-11282
URL: https://issues.apache.org/jira/browse/NIFI-11282
Project: Apache NiFi
Issue Type: Task
Components: Tools and Build
Reporter: Kevin Doran
Assignee: Kevin Doran
Fix For: 1.5.0
{noformat}
[INFO] --- maven-checkstyle-plugin:3.2.0:check (check-style) @
nifi-nar-maven-plugin ---
[WARNING] src/main/java/org/apache/nifi/NarMojo.java:[29,8] (imports)
UnusedImports: Unused import -
org.apache.maven.artifact.repository.RepositoryRequest.
[WARNING] src/main/java/org/apache/nifi/NarMojo.java:[30,8] (imports)
UnusedImports: Unused import -
org.apache.maven.artifact.resolver.ArtifactNotFoundException.
[WARNING] src/main/java/org/apache/nifi/NarMojo.java:[31,8] (imports)
UnusedImports: Unused import -
org.apache.maven.artifact.resolver.ArtifactResolutionException.
[WARNING] src/main/java/org/apache/nifi/NarMojo.java:[984,17] (blocks)
LeftCurly: '{' at column 17 should be on the previous line.
[WARNING]
src/test/java/org/apache/nifi/extension/definition/extraction/ExtensionClassLoaderFactoryTest.java:[127]
(regexp) RegexpSinglelineJava: Line has trailing whitespace.
[INFO]
[INFO] BUILD FAILURE
[INFO]
{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-11274) PutElasticsearchRecord should only add @timestamp field if not null
[
https://issues.apache.org/jira/browse/NIFI-11274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-11274:
---
Fix Version/s: 2.0.0
1.21.0
(was: 1.latest)
(was: 2.latest)
Resolution: Fixed
Status: Resolved (was: Patch Available)
> PutElasticsearchRecord should only add @timestamp field if not null
> ---
>
> Key: NIFI-11274
> URL: https://issues.apache.org/jira/browse/NIFI-11274
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.20.0
>Reporter: Chris Sampson
>Assignee: Chris Sampson
>Priority: Minor
> Fix For: 2.0.0, 1.21.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The {{PutElasticsearchRecord}} processor optionally allows users to configure
> an {{@timestamp}} field using a RecordPath or specified value. When these are
> not set or the configuration results in a {{null}} value, the processor
> currently adds a {{"@timestamp": null}} field to the document being sent to
> Elasticsearch.
> While {{null}}/empty fields can be suppressed by the
> {{ElasticSearchClientServiceImpl}}, this is not always the wanted
> configuration. NiFi shouldn't always add the {{@timestamp}} field to the
> document before sending because with "null suppression" disabled in the
> controller service, the unwanted/unexpected field will be created and sent to
> Elasticsearch.
> The {{@timestamp}} field was added to support Data Streams within
> Elasticsearch. For such data storage, the field will be necessary but for
> other "normal" indices, the field is likely not wanted (even set to {{null}}).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-11278) Release Manager - Release NAR Maven Plugin 1.5.0
Kevin Doran created NIFI-11278: -- Summary: Release Manager - Release NAR Maven Plugin 1.5.0 Key: NIFI-11278 URL: https://issues.apache.org/jira/browse/NIFI-11278 Project: Apache NiFi Issue Type: Task Components: Tools and Build Reporter: Kevin Doran Assignee: Kevin Doran Fix For: nifi-nar-maven-plugin-1.5.0 Release Manager activities related to releasing NAR Maven Plugin 1.5.0. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11217) NiFi NAR Maven Plugin fails to build external NARs with transitive, provided dependencies.
[
https://issues.apache.org/jira/browse/NIFI-11217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17698075#comment-17698075
]
Kevin Doran commented on NIFI-11217:
Credit to Julien G for reporting and helping us identify the issue on the
Apache NiFi Slack:
https://apachenifi.slack.com/archives/C0L9S92JY/p1676561597970849
> NiFi NAR Maven Plugin fails to build external NARs with transitive, provided
> dependencies.
> --
>
> Key: NIFI-11217
> URL: https://issues.apache.org/jira/browse/NIFI-11217
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: nifi-nar-maven-plugin-1.4.0
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Major
> Fix For: nifi-nar-maven-plugin-1.5.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It appears that the NAR maven plugin was benefiting from behavior in older
> version of the maven-dependency-tree library that would resolve artifacts in
> addition to poms when crawling dependendncies. This guaranteed that they
> would be in the local Maven repository/cache when in the Extension
> Documentation generation phase of NAR building.
> Version 1.4.0 of the plugin upgraded maven-dependency-tree to 3.2.0, which
> included this behavior change to only download poms:
> https://github.com/apache/maven-dependency-tree/commit/b330fa93b70e35c70a8afa75f0404cf47d5935d6
>
> This broke building NARs that are external from the Apache NiFi
> repository/project that inherit from (or depend on) NiFi NARs that have
> transitive dependencies marked as provided, because the Extension
> Documentation generation needs the full artifact resolved in order to create
> a working ClassLoader. Not having artifacts resolved results in error
> messages such as:
> {noformat}
> [INFO] --- nifi-nar-maven-plugin:1.4.0:nar (default-nar) @
> nifi-example-processors-nar ---
> [INFO] Copying nifi-example-processors-1.0.jar to
> /Users/kdoran/dev/code/nifi-dependency-example/nifi-inherits-processor-bundle/nifi-example-processors-nar/target/classes/META-INF/bundled-dependencies/nifi-example-processors-1.0.jar
> [INFO] Generating documentation for NiFi extensions in the NAR...
> [INFO] Found NAR dependency of
> org.apache.nifi:nifi-standard-services-api-nar:nar:1.20.0:compile
> [INFO] Found NAR dependency of
> org.apache.nifi:nifi-jetty-bundle:nar:1.20.0:compile
> [INFO] Found a dependency on version 1.20.0 of NiFi API
> [ERROR] Could not generate extensions' documentation
> org.apache.maven.plugin.MojoExecutionException: Failed to create Extension
> Documentation
> at org.apache.nifi.NarMojo.generateDocumentation (NarMojo.java:534)
> at org.apache.nifi.NarMojo.execute (NarMojo.java:505)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by:
[jira] [Updated] (NIFI-11217) NiFi NAR Maven Plugin fails to build external NARs with transitive, provided dependencies.
[
https://issues.apache.org/jira/browse/NIFI-11217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-11217:
---
Status: Patch Available (was: In Progress)
> NiFi NAR Maven Plugin fails to build external NARs with transitive, provided
> dependencies.
> --
>
> Key: NIFI-11217
> URL: https://issues.apache.org/jira/browse/NIFI-11217
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
>Affects Versions: nifi-nar-maven-plugin-1.4.0
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Major
> Fix For: nifi-nar-maven-plugin-1.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> It appears that the NAR maven plugin was benefiting from behavior in older
> version of the maven-dependency-tree library that would resolve artifacts in
> addition to poms when crawling dependendncies. This guaranteed that they
> would be in the local Maven repository/cache when in the Extension
> Documentation generation phase of NAR building.
> Version 1.4.0 of the plugin upgraded maven-dependency-tree to 3.2.0, which
> included this behavior change to only download poms:
> https://github.com/apache/maven-dependency-tree/commit/b330fa93b70e35c70a8afa75f0404cf47d5935d6
>
> This broke building NARs that are external from the Apache NiFi
> repository/project that inherit from (or depend on) NiFi NARs that have
> transitive dependencies marked as provided, because the Extension
> Documentation generation needs the full artifact resolved in order to create
> a working ClassLoader. Not having artifacts resolved results in error
> messages such as:
> {noformat}
> [INFO] --- nifi-nar-maven-plugin:1.4.0:nar (default-nar) @
> nifi-example-processors-nar ---
> [INFO] Copying nifi-example-processors-1.0.jar to
> /Users/kdoran/dev/code/nifi-dependency-example/nifi-inherits-processor-bundle/nifi-example-processors-nar/target/classes/META-INF/bundled-dependencies/nifi-example-processors-1.0.jar
> [INFO] Generating documentation for NiFi extensions in the NAR...
> [INFO] Found NAR dependency of
> org.apache.nifi:nifi-standard-services-api-nar:nar:1.20.0:compile
> [INFO] Found NAR dependency of
> org.apache.nifi:nifi-jetty-bundle:nar:1.20.0:compile
> [INFO] Found a dependency on version 1.20.0 of NiFi API
> [ERROR] Could not generate extensions' documentation
> org.apache.maven.plugin.MojoExecutionException: Failed to create Extension
> Documentation
> at org.apache.nifi.NarMojo.generateDocumentation (NarMojo.java:534)
> at org.apache.nifi.NarMojo.execute (NarMojo.java:505)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:210)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:156)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:566)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:282)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launch
> (Launcher.java:225)
> at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
> (Launcher.java:406)
> at org.codehaus.plexus.classworlds.launcher.Launcher.main
> (Launcher.java:347)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Could not resolve
> local dependency org.apache.nifi:nifi-framework-api:jar:1.20.0
> at
>
[jira] [Updated] (NIFI-11218) Upgrade dependencies in NAR Maven Plugin
[ https://issues.apache.org/jira/browse/NIFI-11218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-11218: --- Status: Patch Available (was: Open) > Upgrade dependencies in NAR Maven Plugin > > > Key: NIFI-11218 > URL: https://issues.apache.org/jira/browse/NIFI-11218 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Affects Versions: nifi-nar-maven-plugin-1.4.0 >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Minor > Fix For: nifi-nar-maven-plugin-1.5.0 > > Time Spent: 10m > Remaining Estimate: 0h > > In investigating NIFI-11217, we observed that a number of core dependencies > for the NiFi NAR Maven Plugin are far outdated, some a full major version > behind. > This task is to bring core maven dependencies for the NiFi NAR Maven Plugin > up to latest versions, which will require some code changes. Specifically, we > depend heavily on maven-dependency 2.x and will need code changes to update > to 3.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11217) NiFi NAR Maven Plugin fails to build external NARs with transitive, provided dependencies.
[
https://issues.apache.org/jira/browse/NIFI-11217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-11217:
---
Description:
It appears that the NAR maven plugin was benefiting from behavior in older
version of the maven-dependency-tree library that would resolve artifacts in
addition to poms when crawling dependendncies. This guaranteed that they would
be in the local Maven repository/cache when in the Extension Documentation
generation phase of NAR building.
Version 1.4.0 of the plugin upgraded maven-dependency-tree to 3.2.0, which
included this behavior change to only download poms:
https://github.com/apache/maven-dependency-tree/commit/b330fa93b70e35c70a8afa75f0404cf47d5935d6
This broke building NARs that are external from the Apache NiFi
repository/project that inherit from (or depend on) NiFi NARs that have
transitive dependencies marked as provided, because the Extension Documentation
generation needs the full artifact resolved in order to create a working
ClassLoader. Not having artifacts resolved results in error messages such as:
{noformat}
[INFO] --- nifi-nar-maven-plugin:1.4.0:nar (default-nar) @
nifi-example-processors-nar ---
[INFO] Copying nifi-example-processors-1.0.jar to
/Users/kdoran/dev/code/nifi-dependency-example/nifi-inherits-processor-bundle/nifi-example-processors-nar/target/classes/META-INF/bundled-dependencies/nifi-example-processors-1.0.jar
[INFO] Generating documentation for NiFi extensions in the NAR...
[INFO] Found NAR dependency of
org.apache.nifi:nifi-standard-services-api-nar:nar:1.20.0:compile
[INFO] Found NAR dependency of
org.apache.nifi:nifi-jetty-bundle:nar:1.20.0:compile
[INFO] Found a dependency on version 1.20.0 of NiFi API
[ERROR] Could not generate extensions' documentation
org.apache.maven.plugin.MojoExecutionException: Failed to create Extension
Documentation
at org.apache.nifi.NarMojo.generateDocumentation (NarMojo.java:534)
at org.apache.nifi.NarMojo.execute (NarMojo.java:505)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Could not resolve
local dependency org.apache.nifi:nifi-framework-api:jar:1.20.0
at
org.apache.nifi.extension.definition.extraction.ExtensionClassLoaderFactory.getProvidedArtifact
(ExtensionClassLoaderFactory.java:224)
at
org.apache.nifi.extension.definition.extraction.ExtensionClassLoaderFactory.createProvidedEntitiesClassLoader
(ExtensionClassLoaderFactory.java:258)
at
org.apache.nifi.extension.definition.extraction.ExtensionClassLoaderFactory.createClassLoader
(ExtensionClassLoaderFactory.java:116)
at
org.apache.nifi.extension.definition.extraction.ExtensionClassLoaderFactory.createClassLoader
(ExtensionClassLoaderFactory.java:122)
at
org.apache.nifi.extension.definition.extraction.ExtensionClassLoaderFactory.createClassLoader
(ExtensionClassLoaderFactory.java:122)
at
org.apache.nifi.extension.definition.extraction.ExtensionClassLoaderFactory.createExtensionClassLoader
[jira] [Created] (NIFI-11218) Upgrade dependencies in NAR Maven Plugin
Kevin Doran created NIFI-11218: -- Summary: Upgrade dependencies in NAR Maven Plugin Key: NIFI-11218 URL: https://issues.apache.org/jira/browse/NIFI-11218 Project: Apache NiFi Issue Type: Improvement Components: Tools and Build Affects Versions: nifi-nar-maven-plugin-1.4.0 Reporter: Kevin Doran Assignee: Kevin Doran Fix For: nifi-nar-maven-plugin-1.5.0 In investigating NIFI-11217, we observed that a number of core dependencies for the NiFi NAR Maven Plugin are far outdated, some a full major version behind. This task is to bring core maven dependencies for the NiFi NAR Maven Plugin up to latest versions, which will require some code changes. Specifically, we depend heavily on maven-dependency 2.x and will need code changes to update to 3.x. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11217) NiFi NAR Maven Plugin fails to build external NARs with transitive, provided dependencies.
Kevin Doran created NIFI-11217:
--
Summary: NiFi NAR Maven Plugin fails to build external NARs with
transitive, provided dependencies.
Key: NIFI-11217
URL: https://issues.apache.org/jira/browse/NIFI-11217
Project: Apache NiFi
Issue Type: Bug
Components: Tools and Build
Affects Versions: nifi-nar-maven-plugin-1.4.0
Reporter: Kevin Doran
Assignee: Kevin Doran
Fix For: nifi-nar-maven-plugin-1.5.0
It appears that the NAR maven plugin was benefiting from behavior in older
version of the maven-dependency-tree library we use for how it resolved
provided artifacts in a way that guaranteed that they would be in the local
Maven repository/cache when in the Extension Documentation generation phase of
NAR building.
Version 1.4.0 of the plugin upgraded this dependency, and broke building NARs
that are external from the Apache NiFi repository/project that inherit from (or
depend on) NiFi NARs that have transitive dependencies marked as provided. This
results in error messages such as:
{noformat}
[INFO] --- nifi-nar-maven-plugin:1.4.0:nar (default-nar) @
nifi-example-processors-nar ---
[INFO] Copying nifi-example-processors-1.0.jar to
/Users/kdoran/dev/code/nifi-dependency-example/nifi-inherits-processor-bundle/nifi-example-processors-nar/target/classes/META-INF/bundled-dependencies/nifi-example-processors-1.0.jar
[INFO] Generating documentation for NiFi extensions in the NAR...
[INFO] Found NAR dependency of
org.apache.nifi:nifi-standard-services-api-nar:nar:1.20.0:compile
[INFO] Found NAR dependency of
org.apache.nifi:nifi-jetty-bundle:nar:1.20.0:compile
[INFO] Found a dependency on version 1.20.0 of NiFi API
[ERROR] Could not generate extensions' documentation
org.apache.maven.plugin.MojoExecutionException: Failed to create Extension
Documentation
at org.apache.nifi.NarMojo.generateDocumentation (NarMojo.java:534)
at org.apache.nifi.NarMojo.execute (NarMojo.java:505)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Could not resolve
local dependency org.apache.nifi:nifi-framework-api:jar:1.20.0
at
org.apache.nifi.extension.definition.extraction.ExtensionClassLoaderFactory.getProvidedArtifact
(ExtensionClassLoaderFactory.java:224)
at
org.apache.nifi.extension.definition.extraction.ExtensionClassLoaderFactory.createProvidedEntitiesClassLoader
(ExtensionClassLoaderFactory.java:258)
at
org.apache.nifi.extension.definition.extraction.ExtensionClassLoaderFactory.createClassLoader
(ExtensionClassLoaderFactory.java:116)
at
org.apache.nifi.extension.definition.extraction.ExtensionClassLoaderFactory.createClassLoader
(ExtensionClassLoaderFactory.java:122)
at
org.apache.nifi.extension.definition.extraction.ExtensionClassLoaderFactory.createClassLoader
(ExtensionClassLoaderFactory.java:122)
at
org.apache.nifi.extension.definition.extraction.ExtensionClassLoaderFactory.createExtensionClassLoader
[jira] [Updated] (NIFI-11193) Improve logging for NiFi Registry GitFlowPersistenceProvider in onConfigured
[ https://issues.apache.org/jira/browse/NIFI-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-11193: --- Fix Version/s: 1.21.0 > Improve logging for NiFi Registry GitFlowPersistenceProvider in onConfigured > > > Key: NIFI-11193 > URL: https://issues.apache.org/jira/browse/NIFI-11193 > Project: Apache NiFi > Issue Type: Improvement > Components: NiFi Registry >Affects Versions: 1.20.0 >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Minor > Fix For: 2.0.0, 1.21.0 > > Time Spent: 40m > Remaining Estimate: 0h > > This swallowed exception makes it difficult to troubleshoot errors: > https://github.com/apache/nifi/blob/65dbbc9e76d618c538f8fc79e4c0343998ca719d/nifi-registry/nifi-registry-core/nifi-registry-framework/src/main/java/org/apache/nifi/registry/provider/flow/git/GitFlowMetaData.java#L191-L193 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11193) Improve logging for NiFi Registry GitFlowPersistenceProvider in onConfigured
[ https://issues.apache.org/jira/browse/NIFI-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-11193: --- Status: Patch Available (was: In Progress) > Improve logging for NiFi Registry GitFlowPersistenceProvider in onConfigured > > > Key: NIFI-11193 > URL: https://issues.apache.org/jira/browse/NIFI-11193 > Project: Apache NiFi > Issue Type: Improvement > Components: NiFi Registry >Affects Versions: 1.20.0 >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Minor > Time Spent: 0.5h > Remaining Estimate: 0h > > This swallowed exception makes it difficult to troubleshoot errors: > https://github.com/apache/nifi/blob/65dbbc9e76d618c538f8fc79e4c0343998ca719d/nifi-registry/nifi-registry-core/nifi-registry-framework/src/main/java/org/apache/nifi/registry/provider/flow/git/GitFlowMetaData.java#L191-L193 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11193) Improve logging for NiFi Registry GitFlowPersistenceProvider in onConfigured
[ https://issues.apache.org/jira/browse/NIFI-11193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-11193: --- Summary: Improve logging for NiFi Registry GitFlowPersistenceProvider in onConfigured (was: Improve logging for NiFi Registry FlowGitPersistenceProvider in onConfigured) > Improve logging for NiFi Registry GitFlowPersistenceProvider in onConfigured > > > Key: NIFI-11193 > URL: https://issues.apache.org/jira/browse/NIFI-11193 > Project: Apache NiFi > Issue Type: Improvement > Components: NiFi Registry >Affects Versions: 1.20.0 >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Minor > > This swallowed exception makes it difficult to troubleshoot errors: > https://github.com/apache/nifi/blob/65dbbc9e76d618c538f8fc79e4c0343998ca719d/nifi-registry/nifi-registry-core/nifi-registry-framework/src/main/java/org/apache/nifi/registry/provider/flow/git/GitFlowMetaData.java#L191-L193 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11193) Improve logging for NiFi Registry FlowGitPersistenceProvider in onConfigured
Kevin Doran created NIFI-11193: -- Summary: Improve logging for NiFi Registry FlowGitPersistenceProvider in onConfigured Key: NIFI-11193 URL: https://issues.apache.org/jira/browse/NIFI-11193 Project: Apache NiFi Issue Type: Improvement Components: NiFi Registry Affects Versions: 1.20.0 Reporter: Kevin Doran Assignee: Kevin Doran This swallowed exception makes it difficult to troubleshoot errors: https://github.com/apache/nifi/blob/65dbbc9e76d618c538f8fc79e4c0343998ca719d/nifi-registry/nifi-registry-core/nifi-registry-framework/src/main/java/org/apache/nifi/registry/provider/flow/git/GitFlowMetaData.java#L191-L193 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-10906) Release NiFi NAR Maven Plugin 1.4.0
[ https://issues.apache.org/jira/browse/NIFI-10906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran resolved NIFI-10906. Resolution: Done > Release NiFi NAR Maven Plugin 1.4.0 > --- > > Key: NIFI-10906 > URL: https://issues.apache.org/jira/browse/NIFI-10906 > Project: Apache NiFi > Issue Type: Task >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Major > Fix For: nifi-nar-maven-plugin-1.4.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11106) QueryRecord can fail to rollback sessions on commit failure.
[
https://issues.apache.org/jira/browse/NIFI-11106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-11106:
---
Attachment: nifi-11106-sample-data-1.txt
> QueryRecord can fail to rollback sessions on commit failure.
>
>
> Key: NIFI-11106
> URL: https://issues.apache.org/jira/browse/NIFI-11106
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.14.0, 1.13.2, 1.15.3, 1.17.0, 1.16.3, 1.18.0, 1.19.1
>Reporter: Kevin Doran
>Priority: Blocker
> Attachments: nifi-11106-sample-data-1.txt,
> nifi-11106-sample-data.txt, query-record-config.json.txt
>
>
> It appears that going back to at least NiFi 1.13.2, there are some
> configurations of QueryRecord that can result flowfiles to be not closed
> properly prior to attempting to commit a session. This causes session commit
> to fail, as a a flow file cannot be written while it is still open for
> reading. These show up as uncaught exceptions in NiFi logs (see below).
> Additionally, failed session commits should be rolled back and reprocessed,
> however, some of these QueryRecord commit failures do not get rolled back
> properly. When this occurs, the content of the flowfile is stuck, uncommitted
> so it will not reach downstream processors and not rolled back so that it
> will land back in the QueryRecord input queue to be reprocessed. This can
> result in data loss for the contents of the stuck flowfile.
> Specifically this has been observed with QueryRecord, GrokReader, and
> FreeFormTextRecordSetWriter.
> *Attached is an example configuration of QueryRecord (including record
> reader/writer) that can result in this behavior.*
> During the time observed, data volume was about 40-78 million records per
> hour, with the uncaught exceptions only occasionally occurring (between 0 and
> 10 times per hour). Of those uncaught exceptions, not all resulting in data
> loss / failed rollback, so that is even more rare.
> *Data characteristics:*
> * For the given QueryRecord config that has include and exclude queries, both
> queries are expected to match some lines in the input flowfile.
> * The flowfile is also expected to contain some unmatched lines, such as
> empty lines, lines of text that don't match either query, or corrupted /
> binary lines that don't decode to ascii intermixed with plaintext lines.
> Example data can be provided upon request.
> Here are the stack traces for how this issue appears on NiFi 1.16.1:
> {noformat}
> 2023-01-19T15:22:58.798926992Z stdout F 2023-01-19 15:22:58,797 ERROR
> [Timer-Driven Process Thread-5] o.a.nifi.processors.standard.QueryRecord
> QueryRecord[id=98518d51-88d8-3000-a38e-d629589cfd5a] Processing halted:
> yielding [1 sec]
> 2023-01-19T15:22:58.798933858Z stdout F java.lang.IllegalStateException:
> Cannot commit session while reading from FlowFile
> 2023-01-19T15:22:58.798940864Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.validateCommitState(StandardProcessSession.java:241)
> 2023-01-19T15:22:58.798957184Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:270)
> 2023-01-19T15:22:58.798960616Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:233)
> 2023-01-19T15:22:58.798963703Z stdout F at
> org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commit(BatchingSessionFactory.java:69)
> 2023-01-19T15:22:58.798967659Z stdout F at
> org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commitAsync(BatchingSessionFactory.java:74)
> 2023-01-19T15:22:58.798970816Z stdout F at
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:28)
> 2023-01-19T15:22:58.798974237Z stdout F at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1354)
> 2023-01-19T15:22:58.798978213Z stdout F at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
> 2023-01-19T15:22:58.79899325Z stdout Fat
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103)
> 2023-01-19T15:22:58.798996758Z stdout F at
> org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> 2023-01-19T15:22:58.799000774Z stdout F at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 2023-01-19T15:22:58.799004017Z stdout F at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> 2023-01-19T15:22:58.799007704Z stdout F at
>
[jira] [Resolved] (NIFI-10599) NAR plugin duplicates class loader dependencies during doc generation
[
https://issues.apache.org/jira/browse/NIFI-10599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran resolved NIFI-10599.
Resolution: Fixed
> NAR plugin duplicates class loader dependencies during doc generation
> -
>
> Key: NIFI-10599
> URL: https://issues.apache.org/jira/browse/NIFI-10599
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: nifi-nar-maven-plugin-1.3.4
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: nifi-nar-maven-plugin-1.4.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When creating the parent class loader hierarchy, the top most NAR ends up
> being in the chain twice, and one of the times it has a null NarArtifact.
> This doesn't impact generating the manifest for any of the NARs provided by
> NiFi because all of them have the Jetty NAR as a parent which doesn't
> actually provided any extensions, so the Jetty libs are just there twice.
> It does however affect a standalone bundle where a controller service API NAR
> doesn't have a parent NAR. In this case the API interface can be loaded from
> the class loader which has a null NAR artifact and gets an NPE trying to
> produce the manifest.
> {code:java}
> Caused by: java.lang.NullPointerException
> Â Â at
> org.apache.nifi.extension.definition.extraction.ExtensionDefinitionFactory.processImplementedInterface
> (ExtensionDefinitionFactory.java:132)
> Â Â at
> org.apache.nifi.extension.definition.extraction.ExtensionDefinitionFactory.addProvidedServiceAPIs
> (ExtensionDefinitionFactory.java:102)
> Â Â at
> org.apache.nifi.extension.definition.extraction.ExtensionDefinitionFactory.getProvidedServiceAPIs
> (ExtensionDefinitionFactory.java:86)
> Â Â at
> org.apache.nifi.extension.definition.extraction.ExtensionDefinitionFactory.createExtensionDefinition
> (ExtensionDefinitionFactory.java:75)
> Â Â at
> org.apache.nifi.extension.definition.extraction.ExtensionDefinitionFactory.discoverExtensions
> (ExtensionDefinitionFactory.java:64)
> Â Â at org.apache.nifi.NarMojo.generateDocumentation (NarMojo.java:621)
> Â Â at org.apache.nifi.NarMojo.execute (NarMojo.java:511) {code}
> An example to reproduce the issue is here:
> [https://github.com/bbende/nifi-dependency-example]
> Â
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-10927) Extensions from parent NAR found when generating extension manifest
[ https://issues.apache.org/jira/browse/NIFI-10927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-10927: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Extensions from parent NAR found when generating extension manifest > --- > > Key: NIFI-10927 > URL: https://issues.apache.org/jira/browse/NIFI-10927 > Project: Apache NiFi > Issue Type: Bug >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: nifi-nar-maven-plugin-1.4.0 > > Time Spent: 20m > Remaining Estimate: 0h > > If NAR-A depends on NAR-B, and NAR-B has extension implementations, they get > included in the manifest of NAR-A, even though we only want them in the > manifest of NAR-B. > This has to do with how we locate the service files in the NAR plugin, and > NiFI has similar code that already handles this case: > https://github.com/apache/nifi/blob/dfdd86cff7b6145a537ebb19114ca938fef35d55/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-nar-utils/src/main/java/org/apache/nifi/nar/StandardExtensionDiscoveringManager.java#L244 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10926) Exclude jdk.tools when generating extension manifest
[ https://issues.apache.org/jira/browse/NIFI-10926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-10926: --- Resolution: Fixed Status: Resolved (was: Patch Available) > Exclude jdk.tools when generating extension manifest > > > Key: NIFI-10926 > URL: https://issues.apache.org/jira/browse/NIFI-10926 > Project: Apache NiFi > Issue Type: Bug >Reporter: Bryan Bende >Assignee: Bryan Bende >Priority: Minor > Fix For: nifi-nar-maven-plugin-1.4.0 > > Time Spent: 10m > Remaining Estimate: 0h > > When processing the the dependencies of a NAR to generate the > extension-manifest, some Hadoop dependencies have an optional dependency on a > system scoped dependency on jdk.tools: > [https://github.com/apache/hadoop/blob/trunk/hadoop-common-project/hadoop-annotations/pom.xml] > If building a NAR with Java 8 that has this transitive dependency, this fails > to resolve after upgrading the maven-dependency-tree plugin to version 3.2.0. > Since this jdk.tools jar was only needed for compiling javadocs in > hadoop-common, we can just exclude it from the classpath during our > generation of extension-manifest. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11106) QueryRecord can fail to rollback sessions on commit failure.
[
https://issues.apache.org/jira/browse/NIFI-11106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-11106:
---
Attachment: nifi-11106-sample-data.txt
> QueryRecord can fail to rollback sessions on commit failure.
>
>
> Key: NIFI-11106
> URL: https://issues.apache.org/jira/browse/NIFI-11106
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.14.0, 1.13.2, 1.15.3, 1.17.0, 1.16.3, 1.18.0, 1.19.1
>Reporter: Kevin Doran
>Priority: Blocker
> Attachments: nifi-11106-sample-data.txt, query-record-config.json.txt
>
>
> It appears that going back to at least NiFi 1.13.2, there are some
> configurations of QueryRecord that can result flowfiles to be not closed
> properly prior to attempting to commit a session. This causes session commit
> to fail, as a a flow file cannot be written while it is still open for
> reading. These show up as uncaught exceptions in NiFi logs (see below).
> Additionally, failed session commits should be rolled back and reprocessed,
> however, some of these QueryRecord commit failures do not get rolled back
> properly. When this occurs, the content of the flowfile is stuck, uncommitted
> so it will not reach downstream processors and not rolled back so that it
> will land back in the QueryRecord input queue to be reprocessed. This can
> result in data loss for the contents of the stuck flowfile.
> Specifically this has been observed with QueryRecord, GrokReader, and
> FreeFormTextRecordSetWriter.
> *Attached is an example configuration of QueryRecord (including record
> reader/writer) that can result in this behavior.*
> During the time observed, data volume was about 40-78 million records per
> hour, with the uncaught exceptions only occasionally occurring (between 0 and
> 10 times per hour). Of those uncaught exceptions, not all resulting in data
> loss / failed rollback, so that is even more rare.
> *Data characteristics:*
> * For the given QueryRecord config that has include and exclude queries, both
> queries are expected to match some lines in the input flowfile.
> * The flowfile is also expected to contain some unmatched lines, such as
> empty lines, lines of text that don't match either query, or corrupted /
> binary lines that don't decode to ascii intermixed with plaintext lines.
> Example data can be provided upon request.
> Here are the stack traces for how this issue appears on NiFi 1.16.1:
> {noformat}
> 2023-01-19T15:22:58.798926992Z stdout F 2023-01-19 15:22:58,797 ERROR
> [Timer-Driven Process Thread-5] o.a.nifi.processors.standard.QueryRecord
> QueryRecord[id=98518d51-88d8-3000-a38e-d629589cfd5a] Processing halted:
> yielding [1 sec]
> 2023-01-19T15:22:58.798933858Z stdout F java.lang.IllegalStateException:
> Cannot commit session while reading from FlowFile
> 2023-01-19T15:22:58.798940864Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.validateCommitState(StandardProcessSession.java:241)
> 2023-01-19T15:22:58.798957184Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:270)
> 2023-01-19T15:22:58.798960616Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:233)
> 2023-01-19T15:22:58.798963703Z stdout F at
> org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commit(BatchingSessionFactory.java:69)
> 2023-01-19T15:22:58.798967659Z stdout F at
> org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commitAsync(BatchingSessionFactory.java:74)
> 2023-01-19T15:22:58.798970816Z stdout F at
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:28)
> 2023-01-19T15:22:58.798974237Z stdout F at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1354)
> 2023-01-19T15:22:58.798978213Z stdout F at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
> 2023-01-19T15:22:58.79899325Z stdout Fat
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103)
> 2023-01-19T15:22:58.798996758Z stdout F at
> org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> 2023-01-19T15:22:58.799000774Z stdout F at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 2023-01-19T15:22:58.799004017Z stdout F at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> 2023-01-19T15:22:58.799007704Z stdout F at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>
[jira] [Updated] (NIFI-11106) QueryRecord can fail to rollback sessions on commit failure.
[
https://issues.apache.org/jira/browse/NIFI-11106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-11106:
---
Attachment: (was: nifi-11106-sample-data.txt)
> QueryRecord can fail to rollback sessions on commit failure.
>
>
> Key: NIFI-11106
> URL: https://issues.apache.org/jira/browse/NIFI-11106
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.14.0, 1.13.2, 1.15.3, 1.17.0, 1.16.3, 1.18.0, 1.19.1
>Reporter: Kevin Doran
>Priority: Blocker
> Attachments: nifi-11106-sample-data.txt, query-record-config.json.txt
>
>
> It appears that going back to at least NiFi 1.13.2, there are some
> configurations of QueryRecord that can result flowfiles to be not closed
> properly prior to attempting to commit a session. This causes session commit
> to fail, as a a flow file cannot be written while it is still open for
> reading. These show up as uncaught exceptions in NiFi logs (see below).
> Additionally, failed session commits should be rolled back and reprocessed,
> however, some of these QueryRecord commit failures do not get rolled back
> properly. When this occurs, the content of the flowfile is stuck, uncommitted
> so it will not reach downstream processors and not rolled back so that it
> will land back in the QueryRecord input queue to be reprocessed. This can
> result in data loss for the contents of the stuck flowfile.
> Specifically this has been observed with QueryRecord, GrokReader, and
> FreeFormTextRecordSetWriter.
> *Attached is an example configuration of QueryRecord (including record
> reader/writer) that can result in this behavior.*
> During the time observed, data volume was about 40-78 million records per
> hour, with the uncaught exceptions only occasionally occurring (between 0 and
> 10 times per hour). Of those uncaught exceptions, not all resulting in data
> loss / failed rollback, so that is even more rare.
> *Data characteristics:*
> * For the given QueryRecord config that has include and exclude queries, both
> queries are expected to match some lines in the input flowfile.
> * The flowfile is also expected to contain some unmatched lines, such as
> empty lines, lines of text that don't match either query, or corrupted /
> binary lines that don't decode to ascii intermixed with plaintext lines.
> Example data can be provided upon request.
> Here are the stack traces for how this issue appears on NiFi 1.16.1:
> {noformat}
> 2023-01-19T15:22:58.798926992Z stdout F 2023-01-19 15:22:58,797 ERROR
> [Timer-Driven Process Thread-5] o.a.nifi.processors.standard.QueryRecord
> QueryRecord[id=98518d51-88d8-3000-a38e-d629589cfd5a] Processing halted:
> yielding [1 sec]
> 2023-01-19T15:22:58.798933858Z stdout F java.lang.IllegalStateException:
> Cannot commit session while reading from FlowFile
> 2023-01-19T15:22:58.798940864Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.validateCommitState(StandardProcessSession.java:241)
> 2023-01-19T15:22:58.798957184Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:270)
> 2023-01-19T15:22:58.798960616Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:233)
> 2023-01-19T15:22:58.798963703Z stdout F at
> org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commit(BatchingSessionFactory.java:69)
> 2023-01-19T15:22:58.798967659Z stdout F at
> org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commitAsync(BatchingSessionFactory.java:74)
> 2023-01-19T15:22:58.798970816Z stdout F at
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:28)
> 2023-01-19T15:22:58.798974237Z stdout F at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1354)
> 2023-01-19T15:22:58.798978213Z stdout F at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
> 2023-01-19T15:22:58.79899325Z stdout Fat
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103)
> 2023-01-19T15:22:58.798996758Z stdout F at
> org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> 2023-01-19T15:22:58.799000774Z stdout F at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 2023-01-19T15:22:58.799004017Z stdout F at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> 2023-01-19T15:22:58.799007704Z stdout F at
>
[jira] [Updated] (NIFI-11106) QueryRecord can fail to rollback sessions on commit failure.
[
https://issues.apache.org/jira/browse/NIFI-11106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-11106:
---
Attachment: nifi-11106-sample-data.txt
> QueryRecord can fail to rollback sessions on commit failure.
>
>
> Key: NIFI-11106
> URL: https://issues.apache.org/jira/browse/NIFI-11106
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.14.0, 1.13.2, 1.15.3, 1.17.0, 1.16.3, 1.18.0, 1.19.1
>Reporter: Kevin Doran
>Priority: Blocker
> Attachments: nifi-11106-sample-data.txt, query-record-config.json.txt
>
>
> It appears that going back to at least NiFi 1.13.2, there are some
> configurations of QueryRecord that can result flowfiles to be not closed
> properly prior to attempting to commit a session. This causes session commit
> to fail, as a a flow file cannot be written while it is still open for
> reading. These show up as uncaught exceptions in NiFi logs (see below).
> Additionally, failed session commits should be rolled back and reprocessed,
> however, some of these QueryRecord commit failures do not get rolled back
> properly. When this occurs, the content of the flowfile is stuck, uncommitted
> so it will not reach downstream processors and not rolled back so that it
> will land back in the QueryRecord input queue to be reprocessed. This can
> result in data loss for the contents of the stuck flowfile.
> Specifically this has been observed with QueryRecord, GrokReader, and
> FreeFormTextRecordSetWriter.
> *Attached is an example configuration of QueryRecord (including record
> reader/writer) that can result in this behavior.*
> During the time observed, data volume was about 40-78 million records per
> hour, with the uncaught exceptions only occasionally occurring (between 0 and
> 10 times per hour). Of those uncaught exceptions, not all resulting in data
> loss / failed rollback, so that is even more rare.
> *Data characteristics:*
> * For the given QueryRecord config that has include and exclude queries, both
> queries are expected to match some lines in the input flowfile.
> * The flowfile is also expected to contain some unmatched lines, such as
> empty lines, lines of text that don't match either query, or corrupted /
> binary lines that don't decode to ascii intermixed with plaintext lines.
> Example data can be provided upon request.
> Here are the stack traces for how this issue appears on NiFi 1.16.1:
> {noformat}
> 2023-01-19T15:22:58.798926992Z stdout F 2023-01-19 15:22:58,797 ERROR
> [Timer-Driven Process Thread-5] o.a.nifi.processors.standard.QueryRecord
> QueryRecord[id=98518d51-88d8-3000-a38e-d629589cfd5a] Processing halted:
> yielding [1 sec]
> 2023-01-19T15:22:58.798933858Z stdout F java.lang.IllegalStateException:
> Cannot commit session while reading from FlowFile
> 2023-01-19T15:22:58.798940864Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.validateCommitState(StandardProcessSession.java:241)
> 2023-01-19T15:22:58.798957184Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:270)
> 2023-01-19T15:22:58.798960616Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:233)
> 2023-01-19T15:22:58.798963703Z stdout F at
> org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commit(BatchingSessionFactory.java:69)
> 2023-01-19T15:22:58.798967659Z stdout F at
> org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commitAsync(BatchingSessionFactory.java:74)
> 2023-01-19T15:22:58.798970816Z stdout F at
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:28)
> 2023-01-19T15:22:58.798974237Z stdout F at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1354)
> 2023-01-19T15:22:58.798978213Z stdout F at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
> 2023-01-19T15:22:58.79899325Z stdout Fat
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103)
> 2023-01-19T15:22:58.798996758Z stdout F at
> org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> 2023-01-19T15:22:58.799000774Z stdout F at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 2023-01-19T15:22:58.799004017Z stdout F at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> 2023-01-19T15:22:58.799007704Z stdout F at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>
[jira] [Updated] (NIFI-11106) QueryRecord can fail to rollback sessions on commit failure.
[
https://issues.apache.org/jira/browse/NIFI-11106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-11106:
---
Attachment: (was: nifi-11106-sample-data.txt)
> QueryRecord can fail to rollback sessions on commit failure.
>
>
> Key: NIFI-11106
> URL: https://issues.apache.org/jira/browse/NIFI-11106
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.14.0, 1.13.2, 1.15.3, 1.17.0, 1.16.3, 1.18.0, 1.19.1
>Reporter: Kevin Doran
>Priority: Blocker
> Attachments: query-record-config.json.txt
>
>
> It appears that going back to at least NiFi 1.13.2, there are some
> configurations of QueryRecord that can result flowfiles to be not closed
> properly prior to attempting to commit a session. This causes session commit
> to fail, as a a flow file cannot be written while it is still open for
> reading. These show up as uncaught exceptions in NiFi logs (see below).
> Additionally, failed session commits should be rolled back and reprocessed,
> however, some of these QueryRecord commit failures do not get rolled back
> properly. When this occurs, the content of the flowfile is stuck, uncommitted
> so it will not reach downstream processors and not rolled back so that it
> will land back in the QueryRecord input queue to be reprocessed. This can
> result in data loss for the contents of the stuck flowfile.
> Specifically this has been observed with QueryRecord, GrokReader, and
> FreeFormTextRecordSetWriter.
> *Attached is an example configuration of QueryRecord (including record
> reader/writer) that can result in this behavior.*
> During the time observed, data volume was about 40-78 million records per
> hour, with the uncaught exceptions only occasionally occurring (between 0 and
> 10 times per hour). Of those uncaught exceptions, not all resulting in data
> loss / failed rollback, so that is even more rare.
> *Data characteristics:*
> * For the given QueryRecord config that has include and exclude queries, both
> queries are expected to match some lines in the input flowfile.
> * The flowfile is also expected to contain some unmatched lines, such as
> empty lines, lines of text that don't match either query, or corrupted /
> binary lines that don't decode to ascii intermixed with plaintext lines.
> Example data can be provided upon request.
> Here are the stack traces for how this issue appears on NiFi 1.16.1:
> {noformat}
> 2023-01-19T15:22:58.798926992Z stdout F 2023-01-19 15:22:58,797 ERROR
> [Timer-Driven Process Thread-5] o.a.nifi.processors.standard.QueryRecord
> QueryRecord[id=98518d51-88d8-3000-a38e-d629589cfd5a] Processing halted:
> yielding [1 sec]
> 2023-01-19T15:22:58.798933858Z stdout F java.lang.IllegalStateException:
> Cannot commit session while reading from FlowFile
> 2023-01-19T15:22:58.798940864Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.validateCommitState(StandardProcessSession.java:241)
> 2023-01-19T15:22:58.798957184Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:270)
> 2023-01-19T15:22:58.798960616Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:233)
> 2023-01-19T15:22:58.798963703Z stdout F at
> org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commit(BatchingSessionFactory.java:69)
> 2023-01-19T15:22:58.798967659Z stdout F at
> org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commitAsync(BatchingSessionFactory.java:74)
> 2023-01-19T15:22:58.798970816Z stdout F at
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:28)
> 2023-01-19T15:22:58.798974237Z stdout F at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1354)
> 2023-01-19T15:22:58.798978213Z stdout F at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
> 2023-01-19T15:22:58.79899325Z stdout Fat
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103)
> 2023-01-19T15:22:58.798996758Z stdout F at
> org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> 2023-01-19T15:22:58.799000774Z stdout F at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 2023-01-19T15:22:58.799004017Z stdout F at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> 2023-01-19T15:22:58.799007704Z stdout F at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>
[jira] [Updated] (NIFI-11106) QueryRecord can fail to rollback sessions on commit failure.
[
https://issues.apache.org/jira/browse/NIFI-11106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-11106:
---
Attachment: nifi-11106-sample-data.txt
> QueryRecord can fail to rollback sessions on commit failure.
>
>
> Key: NIFI-11106
> URL: https://issues.apache.org/jira/browse/NIFI-11106
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 1.14.0, 1.13.2, 1.15.3, 1.17.0, 1.16.3, 1.18.0, 1.19.1
>Reporter: Kevin Doran
>Priority: Blocker
> Attachments: nifi-11106-sample-data.txt, query-record-config.json.txt
>
>
> It appears that going back to at least NiFi 1.13.2, there are some
> configurations of QueryRecord that can result flowfiles to be not closed
> properly prior to attempting to commit a session. This causes session commit
> to fail, as a a flow file cannot be written while it is still open for
> reading. These show up as uncaught exceptions in NiFi logs (see below).
> Additionally, failed session commits should be rolled back and reprocessed,
> however, some of these QueryRecord commit failures do not get rolled back
> properly. When this occurs, the content of the flowfile is stuck, uncommitted
> so it will not reach downstream processors and not rolled back so that it
> will land back in the QueryRecord input queue to be reprocessed. This can
> result in data loss for the contents of the stuck flowfile.
> Specifically this has been observed with QueryRecord, GrokReader, and
> FreeFormTextRecordSetWriter.
> *Attached is an example configuration of QueryRecord (including record
> reader/writer) that can result in this behavior.*
> During the time observed, data volume was about 40-78 million records per
> hour, with the uncaught exceptions only occasionally occurring (between 0 and
> 10 times per hour). Of those uncaught exceptions, not all resulting in data
> loss / failed rollback, so that is even more rare.
> *Data characteristics:*
> * For the given QueryRecord config that has include and exclude queries, both
> queries are expected to match some lines in the input flowfile.
> * The flowfile is also expected to contain some unmatched lines, such as
> empty lines, lines of text that don't match either query, or corrupted /
> binary lines that don't decode to ascii intermixed with plaintext lines.
> Example data can be provided upon request.
> Here are the stack traces for how this issue appears on NiFi 1.16.1:
> {noformat}
> 2023-01-19T15:22:58.798926992Z stdout F 2023-01-19 15:22:58,797 ERROR
> [Timer-Driven Process Thread-5] o.a.nifi.processors.standard.QueryRecord
> QueryRecord[id=98518d51-88d8-3000-a38e-d629589cfd5a] Processing halted:
> yielding [1 sec]
> 2023-01-19T15:22:58.798933858Z stdout F java.lang.IllegalStateException:
> Cannot commit session while reading from FlowFile
> 2023-01-19T15:22:58.798940864Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.validateCommitState(StandardProcessSession.java:241)
> 2023-01-19T15:22:58.798957184Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:270)
> 2023-01-19T15:22:58.798960616Z stdout F at
> org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:233)
> 2023-01-19T15:22:58.798963703Z stdout F at
> org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commit(BatchingSessionFactory.java:69)
> 2023-01-19T15:22:58.798967659Z stdout F at
> org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commitAsync(BatchingSessionFactory.java:74)
> 2023-01-19T15:22:58.798970816Z stdout F at
> org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:28)
> 2023-01-19T15:22:58.798974237Z stdout F at
> org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1354)
> 2023-01-19T15:22:58.798978213Z stdout F at
> org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
> 2023-01-19T15:22:58.79899325Z stdout Fat
> org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103)
> 2023-01-19T15:22:58.798996758Z stdout F at
> org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> 2023-01-19T15:22:58.799000774Z stdout F at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 2023-01-19T15:22:58.799004017Z stdout F at
> java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
> 2023-01-19T15:22:58.799007704Z stdout F at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
>
[jira] [Created] (NIFI-11106) QueryRecord can fail to rollback sessions on commit failure.
Kevin Doran created NIFI-11106:
--
Summary: QueryRecord can fail to rollback sessions on commit
failure.
Key: NIFI-11106
URL: https://issues.apache.org/jira/browse/NIFI-11106
Project: Apache NiFi
Issue Type: Bug
Components: Extensions
Affects Versions: 1.19.1, 1.18.0, 1.16.3, 1.17.0, 1.15.3, 1.13.2, 1.14.0
Reporter: Kevin Doran
Attachments: query-record-config.json.txt
It appears that going back to at least NiFi 1.13.2, there are some
configurations of QueryRecord that can result flowfiles to be not closed
properly prior to attempting to commit a session. This causes session commit to
fail, as a a flow file cannot be written while it is still open for reading.
These show up as uncaught exceptions in NiFi logs (see below).
Additionally, failed session commits should be rolled back and reprocessed,
however, some of these QueryRecord commit failures do not get rolled back
properly. When this occurs, the content of the flowfile is stuck, uncommitted
so it will not reach downstream processors and not rolled back so that it will
land back in the QueryRecord input queue to be reprocessed. This can result in
data loss for the contents of the stuck flowfile.
Specifically this has been observed with QueryRecord, GrokReader, and
FreeFormTextRecordSetWriter.
*Attached is an example configuration of QueryRecord (including record
reader/writer) that can result in this behavior.*
During the time observed, data volume was about 40-78 million records per hour,
with the uncaught exceptions only occasionally occurring (between 0 and 10
times per hour). Of those uncaught exceptions, not all resulting in data loss /
failed rollback, so that is even more rare.
*Data characteristics:*
* For the given QueryRecord config that has include and exclude queries, both
queries are expected to match some lines in the input flowfile.
* The flowfile is also expected to contain some unmatched lines, such as empty
lines, lines of text that don't match either query, or corrupted / binary lines
that don't decode to ascii intermixed with plaintext lines.
Example data can be provided upon request.
Here are the stack traces for how this issue appears on NiFi 1.16.1:
{noformat}
2023-01-19T15:22:58.798926992Z stdout F 2023-01-19 15:22:58,797 ERROR
[Timer-Driven Process Thread-5] o.a.nifi.processors.standard.QueryRecord
QueryRecord[id=98518d51-88d8-3000-a38e-d629589cfd5a] Processing halted:
yielding [1 sec]
2023-01-19T15:22:58.798933858Z stdout F java.lang.IllegalStateException: Cannot
commit session while reading from FlowFile
2023-01-19T15:22:58.798940864Z stdout F at
org.apache.nifi.controller.repository.StandardProcessSession.validateCommitState(StandardProcessSession.java:241)
2023-01-19T15:22:58.798957184Z stdout F at
org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:270)
2023-01-19T15:22:58.798960616Z stdout F at
org.apache.nifi.controller.repository.StandardProcessSession.checkpoint(StandardProcessSession.java:233)
2023-01-19T15:22:58.798963703Z stdout F at
org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commit(BatchingSessionFactory.java:69)
2023-01-19T15:22:58.798967659Z stdout F at
org.apache.nifi.controller.repository.BatchingSessionFactory$HighThroughputSession.commitAsync(BatchingSessionFactory.java:74)
2023-01-19T15:22:58.798970816Z stdout F at
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:28)
2023-01-19T15:22:58.798974237Z stdout F at
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1354)
2023-01-19T15:22:58.798978213Z stdout F at
org.apache.nifi.controller.tasks.ConnectableTask.invoke(ConnectableTask.java:214)
2023-01-19T15:22:58.79899325Z stdout F at
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:103)
2023-01-19T15:22:58.798996758Z stdout F at
org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
2023-01-19T15:22:58.799000774Z stdout F at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
2023-01-19T15:22:58.799004017Z stdout F at
java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
2023-01-19T15:22:58.799007704Z stdout F at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
2023-01-19T15:22:58.799011065Z stdout F at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
2023-01-19T15:22:58.799014058Z stdout F at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
2023-01-19T15:22:58.79901729Z stdout F at
[jira] [Updated] (NIFI-10906) Release NiFi NAR Maven Plugin 1.4.0
[ https://issues.apache.org/jira/browse/NIFI-10906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-10906: --- Status: In Progress (was: Patch Available) > Release NiFi NAR Maven Plugin 1.4.0 > --- > > Key: NIFI-10906 > URL: https://issues.apache.org/jira/browse/NIFI-10906 > Project: Apache NiFi > Issue Type: Task >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Major > Fix For: nifi-nar-maven-plugin-1.4.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10906) Release NiFi NAR Maven Plugin 1.4.0
Kevin Doran created NIFI-10906: -- Summary: Release NiFi NAR Maven Plugin 1.4.0 Key: NIFI-10906 URL: https://issues.apache.org/jira/browse/NIFI-10906 Project: Apache NiFi Issue Type: Task Reporter: Kevin Doran Fix For: nifi-nar-maven-plugin-1.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10905) Bump NAR Maven Plugin checkstyle version
[ https://issues.apache.org/jira/browse/NIFI-10905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-10905: --- Status: Patch Available (was: Open) > Bump NAR Maven Plugin checkstyle version > > > Key: NIFI-10905 > URL: https://issues.apache.org/jira/browse/NIFI-10905 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Minor > Fix For: nifi-nar-maven-plugin-1.3.6 > > Time Spent: 10m > Remaining Estimate: 0h > > Update checkstyle to match NiFi (v9.3, which is the last version that > supports Java 8) > also externalize checkstyle rules into standalone xml file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10905) Bump NAR Maven Plugin checkstyle version
Kevin Doran created NIFI-10905: -- Summary: Bump NAR Maven Plugin checkstyle version Key: NIFI-10905 URL: https://issues.apache.org/jira/browse/NIFI-10905 Project: Apache NiFi Issue Type: Improvement Reporter: Kevin Doran Assignee: Kevin Doran Fix For: nifi-nar-maven-plugin-1.3.6 Update checkstyle to match NiFi (v9.3, which is the last version that supports Java 8) also externalize checkstyle rules into standalone xml file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-10325) make timestamp independant from builders' timezone
[ https://issues.apache.org/jira/browse/NIFI-10325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran resolved NIFI-10325. Resolution: Fixed > make timestamp independant from builders' timezone > -- > > Key: NIFI-10325 > URL: https://issues.apache.org/jira/browse/NIFI-10325 > Project: Apache NiFi > Issue Type: Bug > Components: Tools and Build >Affects Versions: nifi-nar-maven-plugin-1.3.4 >Reporter: Herve Boutemy >Priority: Major > Fix For: nifi-nar-maven-plugin-1.3.6 > > Time Spent: 50m > Remaining Estimate: 0h > > NIFI-9857 fixed most reproducibility issues > but when rebuilding NiFi 1.17.0, a remaining issue was found: the timestamp > in MANIFEST.MF uses local timezone instead of UTC as the format suggests, > then the value is different for users in different timezones > see difference #13 on .nar file in > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/nifi/nifi-1.17.0.diffoscope -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-9656) Publish a Java 11 docker image
[ https://issues.apache.org/jira/browse/NIFI-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-9656: -- Summary: Publish a Java 11 docker image (was: Publish an alternative Java 11 docker image) > Publish a Java 11 docker image > -- > > Key: NIFI-9656 > URL: https://issues.apache.org/jira/browse/NIFI-9656 > Project: Apache NiFi > Issue Type: Wish > Components: Docker >Affects Versions: 1.15.3 > Environment: Docker >Reporter: Christoph Nölle >Assignee: Kevin Doran >Priority: Minor > > There have been requests before to update the official Docker image to Java > 11 (such as [NIFI-9188|https://issues.apache.org/jira/browse/NIFI-9188]). As > I understand, this would be a breaking change for many users, though, and > therefore has been postponed for Nifi 2.0. On the other hand, it would be > quite desirable if one could use Java 11 features in custom processors > (without maintaining a custom Docker image). > A solution could be to keep Java 8 for the default image (e.g. tagged > "1.15.3" = latest) and provide a second image, e.g. "1.15.3-openjdk-11". The > Dockerfile has already been adapted to support building with a Java 11 base > image in [https://github.com/apache/nifi/pull/4460]. >  -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-9656) Publish a Java 11 docker image
[ https://issues.apache.org/jira/browse/NIFI-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-9656: -- Fix Version/s: 1.19.0 Status: Patch Available (was: In Progress) > Publish a Java 11 docker image > -- > > Key: NIFI-9656 > URL: https://issues.apache.org/jira/browse/NIFI-9656 > Project: Apache NiFi > Issue Type: Wish > Components: Docker >Affects Versions: 1.15.3 > Environment: Docker >Reporter: Christoph Nölle >Assignee: Kevin Doran >Priority: Minor > Fix For: 1.19.0 > > > There have been requests before to update the official Docker image to Java > 11 (such as [NIFI-9188|https://issues.apache.org/jira/browse/NIFI-9188]). As > I understand, this would be a breaking change for many users, though, and > therefore has been postponed for Nifi 2.0. On the other hand, it would be > quite desirable if one could use Java 11 features in custom processors > (without maintaining a custom Docker image). > A solution could be to keep Java 8 for the default image (e.g. tagged > "1.15.3" = latest) and provide a second image, e.g. "1.15.3-openjdk-11". The > Dockerfile has already been adapted to support building with a Java 11 base > image in [https://github.com/apache/nifi/pull/4460]. >  -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10820) Change base Docker images for NiFi
[ https://issues.apache.org/jira/browse/NIFI-10820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-10820: --- Status: Patch Available (was: Open) > Change base Docker images for NiFi > -- > > Key: NIFI-10820 > URL: https://issues.apache.org/jira/browse/NIFI-10820 > Project: Apache NiFi > Issue Type: Sub-task > Components: Docker >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Major > Fix For: 1.19.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Pretty much the same work that was done for minifi under NIFI-10701, but for > nifi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-9656) Publish an alternative Java 11 docker image
[ https://issues.apache.org/jira/browse/NIFI-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17635011#comment-17635011 ] Kevin Doran commented on NIFI-9656: --- A number of factors have tipped the scale in favor of changing the NiFi base image over maintaining backwards compatibility: * Many users requesting images for arm64 platform * The current base image, openjdk:8-jre is no longer being maintained Given this, there is a lot of support for moving eclipse-temurin as a new base image, which is one of the popular successors to the openjdk images and it already support multiarch builds. As this will disrupt some users, it seems like a good time to also move to Java 11. Lastly, I think I've found a way to restructure our Docker source / build process to make it much easier to build and publish image variants without a lot of duplication. I'll be looking into this so we can offer Java 17 variants soon. > Publish an alternative Java 11 docker image > --- > > Key: NIFI-9656 > URL: https://issues.apache.org/jira/browse/NIFI-9656 > Project: Apache NiFi > Issue Type: Wish > Components: Docker >Affects Versions: 1.15.3 > Environment: Docker >Reporter: Christoph Nölle >Assignee: Kevin Doran >Priority: Minor > > There have been requests before to update the official Docker image to Java > 11 (such as [NIFI-9188|https://issues.apache.org/jira/browse/NIFI-9188]). As > I understand, this would be a breaking change for many users, though, and > therefore has been postponed for Nifi 2.0. On the other hand, it would be > quite desirable if one could use Java 11 features in custom processors > (without maintaining a custom Docker image). > A solution could be to keep Java 8 for the default image (e.g. tagged > "1.15.3" = latest) and provide a second image, e.g. "1.15.3-openjdk-11". The > Dockerfile has already been adapted to support building with a Java 11 base > image in [https://github.com/apache/nifi/pull/4460]. >  -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-9656) Publish an alternative Java 11 docker image
[ https://issues.apache.org/jira/browse/NIFI-9656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran reassigned NIFI-9656: - Assignee: Kevin Doran > Publish an alternative Java 11 docker image > --- > > Key: NIFI-9656 > URL: https://issues.apache.org/jira/browse/NIFI-9656 > Project: Apache NiFi > Issue Type: Wish > Components: Docker >Affects Versions: 1.15.3 > Environment: Docker >Reporter: Christoph Nölle >Assignee: Kevin Doran >Priority: Minor > > There have been requests before to update the official Docker image to Java > 11 (such as [NIFI-9188|https://issues.apache.org/jira/browse/NIFI-9188]). As > I understand, this would be a breaking change for many users, though, and > therefore has been postponed for Nifi 2.0. On the other hand, it would be > quite desirable if one could use Java 11 features in custom processors > (without maintaining a custom Docker image). > A solution could be to keep Java 8 for the default image (e.g. tagged > "1.15.3" = latest) and provide a second image, e.g. "1.15.3-openjdk-11". The > Dockerfile has already been adapted to support building with a Java 11 base > image in [https://github.com/apache/nifi/pull/4460]. >  -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10701) MiNiFi - Update base docker images
[ https://issues.apache.org/jira/browse/NIFI-10701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-10701: --- Resolution: Done Status: Resolved (was: Patch Available) > MiNiFi - Update base docker images > -- > > Key: NIFI-10701 > URL: https://issues.apache.org/jira/browse/NIFI-10701 > Project: Apache NiFi > Issue Type: Improvement > Components: MiNiFi >Reporter: Ferenc Kis >Assignee: Ferenc Kis >Priority: Blocker > Labels: minifi > Fix For: 1.19.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > As openjdk:8-jre-alpine is discontinued we need to move to a docker image > which is maintained -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10820) Change base Docker images for NiFi
Kevin Doran created NIFI-10820: -- Summary: Change base Docker images for NiFi Key: NIFI-10820 URL: https://issues.apache.org/jira/browse/NIFI-10820 Project: Apache NiFi Issue Type: Sub-task Components: Docker Reporter: Kevin Doran Assignee: Kevin Doran Fix For: 1.19.0 Pretty much the same work that was done for minifi under NIFI-10701, but for nifi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10579) Improve standard out handling
[
https://issues.apache.org/jira/browse/NIFI-10579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17612412#comment-17612412
]
Kevin Doran commented on NIFI-10579:
I would be amenable to this change, and do not have a strong preference for
which approach to go with. [~markap14] [~exceptionfactory] [~joewitt] might
have an opinion on the approach used.
> Improve standard out handling
> -
>
> Key: NIFI-10579
> URL: https://issues.apache.org/jira/browse/NIFI-10579
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration
>Affects Versions: 1.16.3
> Environment: All
>Reporter: Dylan Klomparens
>Priority: Minor
> Labels: easyfix, newbie
>
> h1. Problem statement and context
> NiFi intentionally captures and redirects everything sent to standard out and
> standard error. It does so in the [RunNiFi class, seen
> here|https://github.com/apache/nifi/blob/7823156606ca541ef9cae7192b092efd2cfe4e9a/nifi-bootstrap/src/main/java/org/apache/nifi/bootstrap/RunNiFi.java#L1490].
> This approach has the benefit of assigning logback logger classification to
> output that is sent to standard out and standard error. Thus, messages that
> are printed to standard out are labeled as originating from the
> "{{org.apache.nifi.StdOut}}" logback logger, and output from the "{{NiFi
> logging handler}}" thread. This catches all stray messages that may casually
> be output to standard out or standard error for debugging purposes...
> This approach also has drawbacks. It does not permit the NiFi administrator
> to redirect standard error or standard out easily. For example, if NiFi is
> configured to write all logs to standard out, this "encases" *every* log
> message as if it were written to the "{{org.apache.nifi.StdOut}}" logger at
> the {{INFO}} log level. For example, suppose logback is configured to write
> all messages to the console (standard out) with the message format: [date]
> [log level] [thread] [logger] [message]. All subsequent output would be
> "double wrapped", first being output by the logger it was emitted from, then
> being output by the logger handling standard out, and would look like the
> sample below. (Red is the "wrapping" logger, blue is the original message).
> {color:#DE350B}[date] INFO [NiFi logging handler]
> org.apache.nifi.StdOut{color} {color:#0747A6}[date] [original log level]
> [original thread] [log message]{color}
> This approach has an additional drawback that all log messages emitted from
> {{org.apache.nifi.StdOut}} are output at the {{INFO}} log level. Furthermore,
> all log messages emitted from {{org.apache.nifi.StdErr}} are emitted at the
> {{ERROR}} log level. This secludes the log level from the source logger,
> making log filtering more difficult if the log messages passes through
> standard out or standard error. Every log message is forcibly set to one log
> level.
> h1. Why this should be improved
> It would be beneficial for system administrators to allow redirection of
> standard out and standard error. The ability to pipe log messages to the
> external logging solution of their choice would be an important improvement.
> For example, when NiFi is run in a Docker container, [Docker can send logs
> elsewhere using its configurable log
> driver|https://docs.docker.com/config/containers/logging/configure/]. This
> means Docker is responsible for buffering the logs and forwarding them on to
> an external log solution such as syslog, AWS CloudWatch, Fluent, Google Cloud
> Logging, Splunk, and others.
> It is beneficial to use an external log solution so that logs do not fill up
> the disk of the computer running NiFi.
> h1. Proposed improvement
> There are at least two approaches that would improve NiFi.
> Approach #1: remove the redirection of standard out and standard error in the
> RunNiFi class. This would be the most disruptive approach from a deployment
> perspective, and may affect some existing instances of NiFi.
> Approach #2: add a configuration parameter to bootstrap.conf to disable
> redirection of standard out and standard error. The default would be that
> redirection _does_ still occur. This would be the least disruptive approach,
> and would not affect existing instances of NiFi unless the system
> administrator specifically configures the setting.
> h1. Questions and Implementation
> * Would the NiFi developer community be amenable to this change?
> * If so, which approach is preferred?
> If there is a positive response to this improvement, I will follow the
> [Contributor
> Guide|https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide] and
> implement the desired improvement approach, then submit a pull request.
> Thank you for your time and attention.
--
This message was sent by Atlassian
[jira] [Resolved] (NIFI-10253) NAR Plugin incorrectly handling controller service API with inheritance
[
https://issues.apache.org/jira/browse/NIFI-10253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran resolved NIFI-10253.
Fix Version/s: nifi-nar-maven-plugin-1.3.5
Resolution: Fixed
> NAR Plugin incorrectly handling controller service API with inheritance
> ---
>
> Key: NIFI-10253
> URL: https://issues.apache.org/jira/browse/NIFI-10253
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: nifi-nar-maven-plugin-1.3.4
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Major
> Fix For: nifi-nar-maven-plugin-1.3.5
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> In a previous issue NIFI-10011, we fixed an issue where a controller service
> implementation may have inheritance and one of the super classes may be the
> one that implements the API.
> This is a similar issue, but on the API side. If the API has multiple
> interfaces involved, we need the manifest to say that an implementation
> satisfies all of these interfaces, and currently its only getting the lowest
> level.
> Example...
> API:
> {code:java}
> AtomicDistributedMapCacheClient extends DistributedMapCacheClient {code}
> Implementation:
> {code:java}
> RedisDistributedMapCacheClient {code}
> The manifest contains:
> {code:java}
> "providedApiImplementations" : [ {
> Â Â Â Â Â "group" : "org.apache.nifi",
> Â Â Â Â Â "artifact" : "nifi-standard-services-api-nar",
> Â Â Â Â Â "version" : "1.17.0-SNAPSHOT",
> Â Â Â Â Â "type" :
> "org.apache.nifi.distributed.cache.client.AtomicDistributedMapCacheClient"
> Â Â Â Â } ], {code}
> The provided API implementations should contain the atomic DMC and regular
> DMC, since technically it implements both.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-9554) Support building and running NiFi on arm64/aarch64 platforms such as Apple Silicon M1 Macs
[ https://issues.apache.org/jira/browse/NIFI-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran resolved NIFI-9554. --- Fix Version/s: 1.17.0 Resolution: Fixed > Support building and running NiFi on arm64/aarch64 platforms such as Apple > Silicon M1 Macs > -- > > Key: NIFI-9554 > URL: https://issues.apache.org/jira/browse/NIFI-9554 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Major > Labels: arm64 > Fix For: 1.17.0 > > Time Spent: 2h > Remaining Estimate: 0h > > Some development environments are transitioning to be based on arm64, such as > Apple Silicon M1 Macs. > AWS is also offering arm-based EC2 instances which could be a good target > platform for NiFi clusters. > Some target runtimes for MiNiFi Java also fall into this category, such as > Raspberry Pi. > There are also some native arm64/aarch64 JVMs available that can run on these > platforms without emulation. > Given this, it seems like a good time to adding support for building and > running on arm64/aarch64 in addition to amd64/x86_64. > An initial bit of experimentation shows that the full Maven build fails using > an arm64 JDK, but can succeed with a few changes. This ticket is to introduce > changes that allow Apache NiFi and subprojects such as MiNiFi and Registry to > build and run using a native arm64 JDKs. > Additionally, once this is achieved, add a CI build that targets arm64 > platforms to prevent future changes that would break arm64 compatibility. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10249) Enable Parallel Builds in GitHub Workflow
[ https://issues.apache.org/jira/browse/NIFI-10249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-10249: --- Fix Version/s: 1.17.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Enable Parallel Builds in GitHub Workflow > - > > Key: NIFI-10249 > URL: https://issues.apache.org/jira/browse/NIFI-10249 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 1.17.0 > > Time Spent: 20m > Remaining Estimate: 0h > > GitHub Action runners have a limited number of cores and restricted amount of > memory, resulting in slow build execution. Ubuntu Linux runners have two > cores, macOS runners have three cores, and Windows runners have one core. > Recent improvements to Maven plugins such as the Apache Rat Plugin version > 0.14 resolved warnings related to parallel build execution, so configuring > Maven to run with multiple threads provides some performance improvements > over single-threaded builds. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-9813) NiFi Ranger Plugin will not run on ARM
[
https://issues.apache.org/jira/browse/NIFI-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9813:
--
Status: Patch Available (was: Reopened)
> NiFi Ranger Plugin will not run on ARM
> --
>
> Key: NIFI-9813
> URL: https://issues.apache.org/jira/browse/NIFI-9813
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> See the following test failures for nifi-ranger-plugin on ARM
> {noformat}
> [INFO] -< org.apache.nifi:nifi-ranger-plugin
> >-
> [INFO] Building nifi-ranger-plugin 1.16.0-SNAPSHOT
> [402/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @ nifi-ranger-plugin
> ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-ranger-plugin ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 7 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-ranger-plugin ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR] Tests run: 12, Failures: 0, Errors: 11, Skipped: 1, Time elapsed:
> 0.609 s <<< FAILURE! - in
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testResourceNotFound
> Time elapsed: 0.526 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.UnsatisfiedLinkError:
> /Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp:
> dlopen(/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp,
> 0x0001): tried:
> '/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp' (fat file,
> but missing compatible architecture (have 'i386,x86_64', need 'arm64e')),
> '/usr/lib/jna6957663128700482122.tmp' (no such file)
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testKerberosEnabledWithoutPrincipal
> Time elapsed: 0.009 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ranger.plugin.util.RangerRESTUtils
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testApprovedWithNonDirectAccess
> Time elapsed: 0.007 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
>
[jira] [Updated] (NIFI-9812) nifi-framework-nar-loading-utils native lib test cases fail on ARM platforms
[
https://issues.apache.org/jira/browse/NIFI-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9812:
--
Status: Patch Available (was: Reopened)
> nifi-framework-nar-loading-utils native lib test cases fail on ARM platforms
>
>
> Key: NIFI-9812
> URL: https://issues.apache.org/jira/browse/NIFI-9812
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Looks like the JNI/native-lib loader test cases needs some work for arm64,
> which makes sense.
> {noformat}
> [INFO] --< org.apache.nifi:nifi-framework-nar-loading-utils
> >--
> [INFO] Building nifi-framework-nar-loading-utils 1.16.0-SNAPSHOT
> [94/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-framework-nar-loading-utils ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-framework-nar-loading-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] skip non existing resourceDirectory
> /Users/kdoran/dev/code/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-nar-loading-utils/src/main/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-framework-nar-loading-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-framework-nar-loading-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 19 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-framework-nar-loading-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-framework-nar-loading-utils ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.101
> s <<< FAILURE! - in org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
> [ERROR]
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty
> Time elapsed: 0.066 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni:
>
> dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni,
> 0x0001): tried:
> '/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
> (mach-o file, but is an incompatible architecture (have 'x86_64', need
> 'arm64e')),
> '/usr/lib/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
> (no such file)
> at
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty(TestLoadNativeLibViaSystemProperty.java:139)
> [ERROR]
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryByNarClassLoaderFromSystemProperty
> Time elapsed: 0.021 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/nifi-nar_without_native_lib-1-1.0.nar-unpacked_7297978890074099742_testjni:
>
>
[jira] [Reopened] (NIFI-9812) nifi-framework-nar-loading-utils native lib test cases fail on ARM platforms
[
https://issues.apache.org/jira/browse/NIFI-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran reopened NIFI-9812:
---
> nifi-framework-nar-loading-utils native lib test cases fail on ARM platforms
>
>
> Key: NIFI-9812
> URL: https://issues.apache.org/jira/browse/NIFI-9812
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Looks like the JNI/native-lib loader test cases needs some work for arm64,
> which makes sense.
> {noformat}
> [INFO] --< org.apache.nifi:nifi-framework-nar-loading-utils
> >--
> [INFO] Building nifi-framework-nar-loading-utils 1.16.0-SNAPSHOT
> [94/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-framework-nar-loading-utils ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-framework-nar-loading-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] skip non existing resourceDirectory
> /Users/kdoran/dev/code/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-nar-loading-utils/src/main/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-framework-nar-loading-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-framework-nar-loading-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 19 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-framework-nar-loading-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-framework-nar-loading-utils ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.101
> s <<< FAILURE! - in org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
> [ERROR]
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty
> Time elapsed: 0.066 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni:
>
> dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni,
> 0x0001): tried:
> '/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
> (mach-o file, but is an incompatible architecture (have 'x86_64', need
> 'arm64e')),
> '/usr/lib/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
> (no such file)
> at
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty(TestLoadNativeLibViaSystemProperty.java:139)
> [ERROR]
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryByNarClassLoaderFromSystemProperty
> Time elapsed: 0.021 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/nifi-nar_without_native_lib-1-1.0.nar-unpacked_7297978890074099742_testjni:
>
>
[jira] [Reopened] (NIFI-9813) NiFi Ranger Plugin will not run on ARM
[
https://issues.apache.org/jira/browse/NIFI-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran reopened NIFI-9813:
---
> NiFi Ranger Plugin will not run on ARM
> --
>
> Key: NIFI-9813
> URL: https://issues.apache.org/jira/browse/NIFI-9813
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> See the following test failures for nifi-ranger-plugin on ARM
> {noformat}
> [INFO] -< org.apache.nifi:nifi-ranger-plugin
> >-
> [INFO] Building nifi-ranger-plugin 1.16.0-SNAPSHOT
> [402/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @ nifi-ranger-plugin
> ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-ranger-plugin ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 7 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-ranger-plugin ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR] Tests run: 12, Failures: 0, Errors: 11, Skipped: 1, Time elapsed:
> 0.609 s <<< FAILURE! - in
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testResourceNotFound
> Time elapsed: 0.526 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.UnsatisfiedLinkError:
> /Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp:
> dlopen(/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp,
> 0x0001): tried:
> '/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp' (fat file,
> but missing compatible architecture (have 'i386,x86_64', need 'arm64e')),
> '/usr/lib/jna6957663128700482122.tmp' (no such file)
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testKerberosEnabledWithoutPrincipal
> Time elapsed: 0.009 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ranger.plugin.util.RangerRESTUtils
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testApprovedWithNonDirectAccess
> Time elapsed: 0.007 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
>
[jira] [Reopened] (NIFI-9809) Disable Kudu Tests on arm64 platforms
[
https://issues.apache.org/jira/browse/NIFI-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran reopened NIFI-9809:
---
> Disable Kudu Tests on arm64 platforms
> -
>
> Key: NIFI-9809
> URL: https://issues.apache.org/jira/browse/NIFI-9809
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The kudu-binary artifact is not available for aarch64 (arm64) platforms:
> {noformat}
> Could not resolve dependencies for project
> org.apache.nifi:nifi-kudu-controller-service:jar:1.17.0-SNAPSHOT:
> Could not transfer artifact
> org.apache.kudu:kudu-binary:jar:osx-aarch_64:1.16.0
> {noformat}
> AFAICT, we only use this dependency in test code. so excluding those tests
> from compiling / running when on those platforms should fix the kudu bundle
> build when running on that chip architecture.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-9809) Disable Kudu Tests on arm64 platforms
[
https://issues.apache.org/jira/browse/NIFI-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9809:
--
Status: Patch Available (was: Reopened)
> Disable Kudu Tests on arm64 platforms
> -
>
> Key: NIFI-9809
> URL: https://issues.apache.org/jira/browse/NIFI-9809
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The kudu-binary artifact is not available for aarch64 (arm64) platforms:
> {noformat}
> Could not resolve dependencies for project
> org.apache.nifi:nifi-kudu-controller-service:jar:1.17.0-SNAPSHOT:
> Could not transfer artifact
> org.apache.kudu:kudu-binary:jar:osx-aarch_64:1.16.0
> {noformat}
> AFAICT, we only use this dependency in test code. so excluding those tests
> from compiling / running when on those platforms should fix the kudu bundle
> build when running on that chip architecture.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-9813) NiFi Ranger Plugin will not run on ARM
[
https://issues.apache.org/jira/browse/NIFI-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9813:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> NiFi Ranger Plugin will not run on ARM
> --
>
> Key: NIFI-9813
> URL: https://issues.apache.org/jira/browse/NIFI-9813
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> See the following test failures for nifi-ranger-plugin on ARM
> {noformat}
> [INFO] -< org.apache.nifi:nifi-ranger-plugin
> >-
> [INFO] Building nifi-ranger-plugin 1.16.0-SNAPSHOT
> [402/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @ nifi-ranger-plugin
> ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-ranger-plugin ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 7 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-ranger-plugin ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR] Tests run: 12, Failures: 0, Errors: 11, Skipped: 1, Time elapsed:
> 0.609 s <<< FAILURE! - in
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testResourceNotFound
> Time elapsed: 0.526 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.UnsatisfiedLinkError:
> /Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp:
> dlopen(/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp,
> 0x0001): tried:
> '/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp' (fat file,
> but missing compatible architecture (have 'i386,x86_64', need 'arm64e')),
> '/usr/lib/jna6957663128700482122.tmp' (no such file)
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testKerberosEnabledWithoutPrincipal
> Time elapsed: 0.009 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ranger.plugin.util.RangerRESTUtils
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testApprovedWithNonDirectAccess
> Time elapsed: 0.007 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
>
[jira] [Updated] (NIFI-9812) nifi-framework-nar-loading-utils native lib test cases fail on ARM platforms
[
https://issues.apache.org/jira/browse/NIFI-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9812:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> nifi-framework-nar-loading-utils native lib test cases fail on ARM platforms
>
>
> Key: NIFI-9812
> URL: https://issues.apache.org/jira/browse/NIFI-9812
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Looks like the JNI/native-lib loader test cases needs some work for arm64,
> which makes sense.
> {noformat}
> [INFO] --< org.apache.nifi:nifi-framework-nar-loading-utils
> >--
> [INFO] Building nifi-framework-nar-loading-utils 1.16.0-SNAPSHOT
> [94/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-framework-nar-loading-utils ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-framework-nar-loading-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] skip non existing resourceDirectory
> /Users/kdoran/dev/code/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-nar-loading-utils/src/main/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-framework-nar-loading-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-framework-nar-loading-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 19 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-framework-nar-loading-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-framework-nar-loading-utils ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.101
> s <<< FAILURE! - in org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
> [ERROR]
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty
> Time elapsed: 0.066 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni:
>
> dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni,
> 0x0001): tried:
> '/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
> (mach-o file, but is an incompatible architecture (have 'x86_64', need
> 'arm64e')),
> '/usr/lib/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
> (no such file)
> at
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty(TestLoadNativeLibViaSystemProperty.java:139)
> [ERROR]
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryByNarClassLoaderFromSystemProperty
> Time elapsed: 0.021 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/nifi-nar_without_native_lib-1-1.0.nar-unpacked_7297978890074099742_testjni:
>
>
[jira] [Updated] (NIFI-9809) Disable Kudu Tests on arm64 platforms
[
https://issues.apache.org/jira/browse/NIFI-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9809:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Disable Kudu Tests on arm64 platforms
> -
>
> Key: NIFI-9809
> URL: https://issues.apache.org/jira/browse/NIFI-9809
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The kudu-binary artifact is not available for aarch64 (arm64) platforms:
> {noformat}
> Could not resolve dependencies for project
> org.apache.nifi:nifi-kudu-controller-service:jar:1.17.0-SNAPSHOT:
> Could not transfer artifact
> org.apache.kudu:kudu-binary:jar:osx-aarch_64:1.16.0
> {noformat}
> AFAICT, we only use this dependency in test code. so excluding those tests
> from compiling / running when on those platforms should fix the kudu bundle
> build when running on that chip architecture.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-8322) build failed on AArch64, Fedora 33
[ https://issues.apache.org/jira/browse/NIFI-8322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran resolved NIFI-8322. --- Fix Version/s: 1.17.0 Resolution: Duplicate This is fixed as part of NIFI-9554, closing duplicate issue. > build failed on AArch64, Fedora 33 > --- > > Key: NIFI-8322 > URL: https://issues.apache.org/jira/browse/NIFI-8322 > Project: Apache NiFi > Issue Type: Bug >Reporter: Lutz Weischer >Priority: Major > Fix For: 1.17.0 > > > [jw@cn05 nifi]$ mvn clean install -DskipTests > ... > [INFO] --- maven-remote-resources-plugin:1.7.0:process > (process-resource-bundles) @ nifi-kudu-bundle --- > [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4 > [INFO] Copying 3 resources from 1 bundle. > [INFO] > [INFO] --- maven-compiler-plugin:3.8.1:testCompile (groovy-tests) @ > nifi-kudu-bundle --- > [INFO] No sources to compile > [INFO] > [INFO] --- maven-site-plugin:3.7.1:attach-descriptor (attach-descriptor) @ > nifi-kudu-bundle --- > [INFO] No site descriptor found: nothing to attach. > [INFO] > [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ > nifi-kudu-bundle --- > [INFO] Installing > /home/jw/apache/nifi/nifi-nar-bundles/nifi-kudu-bundle/pom.xml to > /home/jw/.m2/repository/org/apache/nifi/nifi-kudu-bundle/1.14.0-SNAPSHOT/nifi-kudu-bundle-1.14.0-SNAPSHOT.pom > [INFO] > [INFO] < org.apache.nifi:nifi-kudu-processors > > > [INFO] Building nifi-kudu-processors 1.14.0-SNAPSHOT > [193/506] > [INFO] [ jar > ]- > [INFO] > > [INFO] Reactor Summary for nifi 1.14.0-SNAPSHOT: > [INFO] > [INFO] nifi ... SUCCESS [ 4.040 > s] > [INFO] nifi-api ... SUCCESS [ 12.535 > s] > [INFO] nifi-commons ... SUCCESS [ 0.185 > s] > [INFO] nifi-utils . SUCCESS [ 19.467 > s] > [INFO] nifi-security-utils-api SUCCESS [ 11.197 > s] > [INFO] nifi-properties SUCCESS [ 8.688 > s] > [INFO] nifi-security-utils SUCCESS [ 30.187 > s] > [INFO] nifi-framework-api . SUCCESS [ 12.632 > s] > [INFO] nifi-nar-bundles ... SUCCESS [ 0.987 > s] > [INFO] nifi-framework-bundle .. SUCCESS [ 0.145 > s] > [INFO] nifi-framework . SUCCESS [ 0.135 > s] > [INFO] nifi-properties-loader . SUCCESS [ 13.949 > s] > [INFO] nifi-data-provenance-utils . SUCCESS [ 14.710 > s] > [INFO] nifi-parameter . SUCCESS [ 7.130 > s] > [INFO] nifi-uuid5 . SUCCESS [ 2.995 > s] > [INFO] nifi-expression-language ... SUCCESS [ 26.723 > s] > [INFO] nifi-flowfile-packager . SUCCESS [ 6.828 > s] > [INFO] nifi-hl7-query-language SUCCESS [ 10.843 > s] > [INFO] nifi-json-utils SUCCESS [ 3.206 > s] > [INFO] nifi-logging-utils . SUCCESS [ 2.965 > s] > [INFO] nifi-metrics ... SUCCESS [ 8.832 > s] > [INFO] nifi-record SUCCESS [ 11.556 > s] > [INFO] nifi-record-path ... SUCCESS [ 14.880 > s] > [INFO] nifi-rocksdb-utils . SUCCESS [ 7.284 > s] > [INFO] nifi-schema-utils .. SUCCESS [ 8.517 > s] > [INFO] nifi-client-dto SUCCESS [ 14.054 > s] > [INFO] nifi-site-to-site-client ... SUCCESS [ 24.203 > s] > [INFO] nifi-socket-utils .. SUCCESS [ 14.809 > s] > [INFO] nifi-web-utils . SUCCESS [ 5.345 > s] > [INFO] nifi-write-ahead-log ... SUCCESS [ 13.261 > s] > [INFO] nifi-server-api SUCCESS [ 3.137 > s] > [INFO] nifi-bootstrap . SUCCESS [ 16.978 > s] > [INFO] nifi-nar-utils . SUCCESS [ 15.482 > s] > [INFO] nifi-framework-nar-utils ... SUCCESS [ 9.073 > s] > [INFO] nifi-mock-authorizer ... SUCCESS [ 3.175 > s] > [INFO] nifi-framework-authorization ... SUCCESS [
[jira] [Resolved] (NIFI-7846) Supporting os.arch aarch64 issues
[ https://issues.apache.org/jira/browse/NIFI-7846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran resolved NIFI-7846. --- Fix Version/s: 1.17.0 Resolution: Duplicate This is fixed as part of NIFI-9554, closing duplicate issue. > Supporting os.arch aarch64 issues > - > > Key: NIFI-7846 > URL: https://issues.apache.org/jira/browse/NIFI-7846 > Project: Apache NiFi > Issue Type: Bug > Components: Configuration Management >Affects Versions: 1.12.0 > Environment: os.arch=aarch64 >Reporter: libindas >Priority: Major > Labels: AWS, features > Fix For: 1.17.0 > > > [https://snippi.com/s/bzd8w76] > Â -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10248) Setup CI jobs for arm64 platforms
Kevin Doran created NIFI-10248: -- Summary: Setup CI jobs for arm64 platforms Key: NIFI-10248 URL: https://issues.apache.org/jira/browse/NIFI-10248 Project: Apache NiFi Issue Type: Improvement Components: Tools and Build Reporter: Kevin Doran NIFI-9554 adds arm64 compatibility for NiFi. To avoid regression with new development, we should add at least one arm64 platform CI job to check PRs on our GitHubs action workflows. At the time of creating this ticket, it is unclear the extent to which GitHub actions supports this, if at all. For efficiency, and to avoid requiring additional CI jobs, we should see if this could be combined with a Java version or localization/language variant, so that the total number of CI builds we have today does not increase. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-9554) Support building and running NiFi on arm64/aarch64 platforms such as Apple Silicon M1 Macs
[ https://issues.apache.org/jira/browse/NIFI-9554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-9554: -- Labels: arm64 (was: ) > Support building and running NiFi on arm64/aarch64 platforms such as Apple > Silicon M1 Macs > -- > > Key: NIFI-9554 > URL: https://issues.apache.org/jira/browse/NIFI-9554 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Major > Labels: arm64 > Time Spent: 2h > Remaining Estimate: 0h > > Some development environments are transitioning to be based on arm64, such as > Apple Silicon M1 Macs. > AWS is also offering arm-based EC2 instances which could be a good target > platform for NiFi clusters. > Some target runtimes for MiNiFi Java also fall into this category, such as > Raspberry Pi. > There are also some native arm64/aarch64 JVMs available that can run on these > platforms without emulation. > Given this, it seems like a good time to adding support for building and > running on arm64/aarch64 in addition to amd64/x86_64. > An initial bit of experimentation shows that the full Maven build fails using > an arm64 JDK, but can succeed with a few changes. This ticket is to introduce > changes that allow Apache NiFi and subprojects such as MiNiFi and Registry to > build and run using a native arm64 JDKs. > Additionally, once this is achieved, add a CI build that targets arm64 > platforms to prevent future changes that would break arm64 compatibility. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-9813) NiFi Ranger Plugin will not run on ARM
[
https://issues.apache.org/jira/browse/NIFI-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9813:
--
Fix Version/s: 1.17.0
Status: Patch Available (was: In Progress)
> NiFi Ranger Plugin will not run on ARM
> --
>
> Key: NIFI-9813
> URL: https://issues.apache.org/jira/browse/NIFI-9813
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> See the following test failures for nifi-ranger-plugin on ARM
> {noformat}
> [INFO] -< org.apache.nifi:nifi-ranger-plugin
> >-
> [INFO] Building nifi-ranger-plugin 1.16.0-SNAPSHOT
> [402/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @ nifi-ranger-plugin
> ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-ranger-plugin ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 7 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-ranger-plugin ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR] Tests run: 12, Failures: 0, Errors: 11, Skipped: 1, Time elapsed:
> 0.609 s <<< FAILURE! - in
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testResourceNotFound
> Time elapsed: 0.526 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.UnsatisfiedLinkError:
> /Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp:
> dlopen(/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp,
> 0x0001): tried:
> '/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp' (fat file,
> but missing compatible architecture (have 'i386,x86_64', need 'arm64e')),
> '/usr/lib/jna6957663128700482122.tmp' (no such file)
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testKerberosEnabledWithoutPrincipal
> Time elapsed: 0.009 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ranger.plugin.util.RangerRESTUtils
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testApprovedWithNonDirectAccess
> Time elapsed: 0.007 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating
[jira] [Updated] (NIFI-9813) NiFi Ranger Plugin will not run on ARM
[
https://issues.apache.org/jira/browse/NIFI-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9813:
--
Summary: NiFi Ranger Plugin will not run on ARM (was: NiFi Ranger Plugin
may have issues on ARM)
> NiFi Ranger Plugin will not run on ARM
> --
>
> Key: NIFI-9813
> URL: https://issues.apache.org/jira/browse/NIFI-9813
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
>
> See the following test failures for nifi-ranger-plugin on ARM
> {noformat}
> [INFO] -< org.apache.nifi:nifi-ranger-plugin
> >-
> [INFO] Building nifi-ranger-plugin 1.16.0-SNAPSHOT
> [402/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @ nifi-ranger-plugin
> ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-ranger-plugin ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 7 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-ranger-plugin ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR] Tests run: 12, Failures: 0, Errors: 11, Skipped: 1, Time elapsed:
> 0.609 s <<< FAILURE! - in
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testResourceNotFound
> Time elapsed: 0.526 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.UnsatisfiedLinkError:
> /Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp:
> dlopen(/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp,
> 0x0001): tried:
> '/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp' (fat file,
> but missing compatible architecture (have 'i386,x86_64', need 'arm64e')),
> '/usr/lib/jna6957663128700482122.tmp' (no such file)
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testKerberosEnabledWithoutPrincipal
> Time elapsed: 0.009 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ranger.plugin.util.RangerRESTUtils
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testApprovedWithNonDirectAccess
> Time elapsed: 0.007 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
>
[jira] [Updated] (NIFI-9812) nifi-framework-nar-loading-utils native lib test cases fail on ARM platforms
[
https://issues.apache.org/jira/browse/NIFI-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9812:
--
Fix Version/s: 1.17.0
Status: Patch Available (was: In Progress)
> nifi-framework-nar-loading-utils native lib test cases fail on ARM platforms
>
>
> Key: NIFI-9812
> URL: https://issues.apache.org/jira/browse/NIFI-9812
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Looks like the JNI/native-lib loader test cases needs some work for arm64,
> which makes sense.
> {noformat}
> [INFO] --< org.apache.nifi:nifi-framework-nar-loading-utils
> >--
> [INFO] Building nifi-framework-nar-loading-utils 1.16.0-SNAPSHOT
> [94/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-framework-nar-loading-utils ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-framework-nar-loading-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] skip non existing resourceDirectory
> /Users/kdoran/dev/code/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-nar-loading-utils/src/main/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-framework-nar-loading-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-framework-nar-loading-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 19 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-framework-nar-loading-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-framework-nar-loading-utils ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.101
> s <<< FAILURE! - in org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
> [ERROR]
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty
> Time elapsed: 0.066 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni:
>
> dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni,
> 0x0001): tried:
> '/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
> (mach-o file, but is an incompatible architecture (have 'x86_64', need
> 'arm64e')),
> '/usr/lib/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
> (no such file)
> at
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty(TestLoadNativeLibViaSystemProperty.java:139)
> [ERROR]
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryByNarClassLoaderFromSystemProperty
> Time elapsed: 0.021 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/nifi-nar_without_native_lib-1-1.0.nar-unpacked_7297978890074099742_testjni:
>
>
[jira] [Updated] (NIFI-9809) Disable Kudu Tests on arm64 platforms
[
https://issues.apache.org/jira/browse/NIFI-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9809:
--
Fix Version/s: 1.17.0
> Disable Kudu Tests on arm64 platforms
> -
>
> Key: NIFI-9809
> URL: https://issues.apache.org/jira/browse/NIFI-9809
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The kudu-binary artifact is not available for aarch64 (arm64) platforms:
> {noformat}
> Could not resolve dependencies for project
> org.apache.nifi:nifi-kudu-controller-service:jar:1.17.0-SNAPSHOT:
> Could not transfer artifact
> org.apache.kudu:kudu-binary:jar:osx-aarch_64:1.16.0
> {noformat}
> AFAICT, we only use this dependency in test code. so excluding those tests
> from compiling / running when on those platforms should fix the kudu bundle
> build when running on that chip architecture.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-9813) NiFi Ranger Plugin may have issues on ARM
[
https://issues.apache.org/jira/browse/NIFI-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17567493#comment-17567493
]
Kevin Doran commented on NIFI-9813:
---
So the issue here is that
[RagnerRESTUtils|https://github.com/apache/ranger/blob/e10a247cccb9db324a0ddbe3b53c3dcb4b271ad4/agents-common/src/main/java/org/apache/ranger/plugin/util/RangerRESTUtils.java#L94],
uses a [gethostname4j|https://github.com/mattsheppard/gethostname4j], a
library that uses JNA in order to make a native/system call to get the host's
hostname.
If this is the only JNA/native component, it looks like a future version of
Ranger could use a different, pure-Java approach, and we could support Ranger
integration on arm64 platforms, but for now, the only option appears to be
excluding the Ranger extensions when not on x86_64 architectures.
> NiFi Ranger Plugin may have issues on ARM
> -
>
> Key: NIFI-9813
> URL: https://issues.apache.org/jira/browse/NIFI-9813
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Priority: Minor
>
> See the following test failures for nifi-ranger-plugin on ARM
> {noformat}
> [INFO] -< org.apache.nifi:nifi-ranger-plugin
> >-
> [INFO] Building nifi-ranger-plugin 1.16.0-SNAPSHOT
> [402/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @ nifi-ranger-plugin
> ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-ranger-plugin ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 7 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-ranger-plugin ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR] Tests run: 12, Failures: 0, Errors: 11, Skipped: 1, Time elapsed:
> 0.609 s <<< FAILURE! - in
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testResourceNotFound
> Time elapsed: 0.526 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.UnsatisfiedLinkError:
> /Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp:
> dlopen(/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp,
> 0x0001): tried:
> '/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp' (fat file,
> but missing compatible architecture (have 'i386,x86_64', need 'arm64e')),
> '/usr/lib/jna6957663128700482122.tmp' (no such file)
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testKerberosEnabledWithoutPrincipal
> Time elapsed: 0.009 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
>
[jira] [Assigned] (NIFI-9813) NiFi Ranger Plugin may have issues on ARM
[
https://issues.apache.org/jira/browse/NIFI-9813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran reassigned NIFI-9813:
-
Assignee: Kevin Doran
> NiFi Ranger Plugin may have issues on ARM
> -
>
> Key: NIFI-9813
> URL: https://issues.apache.org/jira/browse/NIFI-9813
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
>
> See the following test failures for nifi-ranger-plugin on ARM
> {noformat}
> [INFO] -< org.apache.nifi:nifi-ranger-plugin
> >-
> [INFO] Building nifi-ranger-plugin 1.16.0-SNAPSHOT
> [402/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @ nifi-ranger-plugin
> ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-ranger-plugin ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-ranger-plugin ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 7 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-ranger-plugin ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-ranger-plugin ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-ranger-plugin ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR] Tests run: 12, Failures: 0, Errors: 11, Skipped: 1, Time elapsed:
> 0.609 s <<< FAILURE! - in
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testResourceNotFound
> Time elapsed: 0.526 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.UnsatisfiedLinkError:
> /Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp:
> dlopen(/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp,
> 0x0001): tried:
> '/Users/kdoran/Library/Caches/JNA/temp/jna6957663128700482122.tmp' (fat file,
> but missing compatible architecture (have 'i386,x86_64', need 'arm64e')),
> '/usr/lib/jna6957663128700482122.tmp' (no such file)
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testKerberosEnabledWithoutPrincipal
> Time elapsed: 0.009 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> Caused by: java.lang.NoClassDefFoundError: Could not initialize class
> org.apache.ranger.plugin.util.RangerRESTUtils
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
> [ERROR]
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.testApprovedWithNonDirectAccess
> Time elapsed: 0.007 s <<< ERROR!
> org.apache.nifi.authorization.exception.AuthorizerCreationException: Error
> creating RangerBasePlugin
> at
> org.apache.nifi.ranger.authorization.TestRangerNiFiAuthorizer.setup(TestRangerNiFiAuthorizer.java:93)
>
[jira] [Assigned] (NIFI-9812) nifi-framework-nar-loading-utils native lib test cases fail on ARM platforms
[
https://issues.apache.org/jira/browse/NIFI-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran reassigned NIFI-9812:
-
Assignee: Kevin Doran
> nifi-framework-nar-loading-utils native lib test cases fail on ARM platforms
>
>
> Key: NIFI-9812
> URL: https://issues.apache.org/jira/browse/NIFI-9812
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
>
> Looks like the JNI/native-lib loader test cases needs some work for arm64,
> which makes sense.
> {noformat}
> [INFO] --< org.apache.nifi:nifi-framework-nar-loading-utils
> >--
> [INFO] Building nifi-framework-nar-loading-utils 1.16.0-SNAPSHOT
> [94/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-framework-nar-loading-utils ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-framework-nar-loading-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] skip non existing resourceDirectory
> /Users/kdoran/dev/code/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-nar-loading-utils/src/main/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-framework-nar-loading-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-framework-nar-loading-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 19 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-framework-nar-loading-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-framework-nar-loading-utils ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.101
> s <<< FAILURE! - in org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
> [ERROR]
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty
> Time elapsed: 0.066 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni:
>
> dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni,
> 0x0001): tried:
> '/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
> (mach-o file, but is an incompatible architecture (have 'x86_64', need
> 'arm64e')),
> '/usr/lib/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
> (no such file)
> at
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty(TestLoadNativeLibViaSystemProperty.java:139)
> [ERROR]
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryByNarClassLoaderFromSystemProperty
> Time elapsed: 0.021 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/nifi-nar_without_native_lib-1-1.0.nar-unpacked_7297978890074099742_testjni:
>
> dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/nifi-nar_without_native_lib-1-1.0.nar-unpacked_7297978890074099742_testjni,
> 0x0001): tried:
>
[jira] [Updated] (NIFI-9812) nifi-framework-nar-loading-utils native lib test cases fail on ARM platforms
[
https://issues.apache.org/jira/browse/NIFI-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9812:
--
Summary: nifi-framework-nar-loading-utils native lib test cases fail on ARM
platforms (was: nifi-framework-nar-loading-utils unable to load native libs on
ARM platforms)
> nifi-framework-nar-loading-utils native lib test cases fail on ARM platforms
>
>
> Key: NIFI-9812
> URL: https://issues.apache.org/jira/browse/NIFI-9812
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Priority: Minor
>
> Looks like the JNI/native-lib loader test cases needs some work for arm64,
> which makes sense.
> {noformat}
> [INFO] --< org.apache.nifi:nifi-framework-nar-loading-utils
> >--
> [INFO] Building nifi-framework-nar-loading-utils 1.16.0-SNAPSHOT
> [94/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- buildnumber-maven-plugin:1.4:create (default) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-framework-nar-loading-utils ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-framework-nar-loading-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] skip non existing resourceDirectory
> /Users/kdoran/dev/code/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-nar-loading-utils/src/main/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-framework-nar-loading-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-framework-nar-loading-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 19 resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-framework-nar-loading-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-framework-nar-loading-utils ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-framework-nar-loading-utils ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.101
> s <<< FAILURE! - in org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
> [ERROR]
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty
> Time elapsed: 0.066 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni:
>
> dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni,
> 0x0001): tried:
> '/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
> (mach-o file, but is an incompatible architecture (have 'x86_64', need
> 'arm64e')),
> '/usr/lib/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
> (no such file)
> at
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty(TestLoadNativeLibViaSystemProperty.java:139)
> [ERROR]
> org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryByNarClassLoaderFromSystemProperty
> Time elapsed: 0.021 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/nifi-nar_without_native_lib-1-1.0.nar-unpacked_7297978890074099742_testjni:
>
>
[jira] [Updated] (NIFI-9812) nifi-framework-nar-loading-utils unable to load native libs on ARM platforms
[
https://issues.apache.org/jira/browse/NIFI-9812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9812:
--
Description:
Looks like the JNI/native-lib loader test cases needs some work for arm64,
which makes sense.
{noformat}
[INFO] --< org.apache.nifi:nifi-framework-nar-loading-utils >--
[INFO] Building nifi-framework-nar-loading-utils 1.16.0-SNAPSHOT [94/642]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
nifi-framework-nar-loading-utils ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
nifi-framework-nar-loading-utils ---
[INFO]
[INFO] --- buildnumber-maven-plugin:1.4:create (default) @
nifi-framework-nar-loading-utils ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.7.0:process
(process-resource-bundles) @ nifi-framework-nar-loading-utils ---
[INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
[INFO] Copying 3 resources from 1 bundle.
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
nifi-framework-nar-loading-utils ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] skip non existing resourceDirectory
/Users/kdoran/dev/code/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-nar-loading-utils/src/main/resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
nifi-framework-nar-loading-utils ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources) @
nifi-framework-nar-loading-utils ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] Copying 19 resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
nifi-framework-nar-loading-utils ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
nifi-framework-nar-loading-utils ---
[INFO] Changes detected - recompiling the module!
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
nifi-framework-nar-loading-utils ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
[ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.101 s
<<< FAILURE! - in org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty
[ERROR]
org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty
Time elapsed: 0.066 s <<< ERROR!
java.lang.UnsatisfiedLinkError:
/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni:
dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni,
0x0001): tried:
'/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni'
(mach-o file, but is an incompatible architecture (have 'x86_64', need
'arm64e')),
'/usr/lib/901ce22d-a226-479b-baa1-b08aace5ec73_6588104464077247053_testjni' (no
such file)
at
org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryBy2InstanceClassLoadersFromSystemProperty(TestLoadNativeLibViaSystemProperty.java:139)
[ERROR]
org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryByNarClassLoaderFromSystemProperty
Time elapsed: 0.021 s <<< ERROR!
java.lang.UnsatisfiedLinkError:
/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/nifi-nar_without_native_lib-1-1.0.nar-unpacked_7297978890074099742_testjni:
dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/nifi-nar_without_native_lib-1-1.0.nar-unpacked_7297978890074099742_testjni,
0x0001): tried:
'/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/nifi-nar_without_native_lib-1-1.0.nar-unpacked_7297978890074099742_testjni'
(mach-o file, but is an incompatible architecture (have 'x86_64', need
'arm64e')),
'/usr/lib/nifi-nar_without_native_lib-1-1.0.nar-unpacked_7297978890074099742_testjni'
(no such file)
at
org.apache.nifi.nar.TestLoadNativeLibViaSystemProperty.testLoadSameLibraryByNarClassLoaderFromSystemProperty(TestLoadNativeLibViaSystemProperty.java:97)
[INFO] Running org.apache.nifi.nar.TestNarLoader
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.063 s
- in
[jira] [Assigned] (NIFI-9811) QuestDB does not work on ARM
[
https://issues.apache.org/jira/browse/NIFI-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran reassigned NIFI-9811:
-
Assignee: Kevin Doran
> QuestDB does not work on ARM
>
>
> Key: NIFI-9811
> URL: https://issues.apache.org/jira/browse/NIFI-9811
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Major
>
> Judging from this open issue, it does not appear they will be adding support:
> https://github.com/questdb/questdb/issues/569
> so for ARM, we will need to exclude this or find an alternative.
> Here is test failure output showing the runtime issues:
> {noformat}
> [INFO] Running
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest
> [ERROR] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.026
> s <<< FAILURE! - in
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest.testReadingEmptyRepository
> Time elapsed: 0.025 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> io.questdb.log.LogError: Error creating log writer
> java.lang.NullPointerException:
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest.testWritingThenReadingComponents
> Time elapsed: 0.001 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> java.lang.NoClassDefFoundError: Could not initialize class
> io.questdb.cutlass.text.types.InputFormatConfiguration
> java.lang.NullPointerException:
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest.testReadingLimitedByPreferredDataPoints
> Time elapsed: 0 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> java.lang.NoClassDefFoundError: Could not initialize class
> io.questdb.cutlass.text.types.InputFormatConfiguration
> java.lang.NullPointerException:
> [INFO] Running
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForNodeTest
> [ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 1, Time elapsed: 0 s
> <<< FAILURE! - in
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForNodeTest
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForNodeTest.testReadingEmptyRepository
> Time elapsed: 0 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> java.lang.NoClassDefFoundError: Could not initialize class
> io.questdb.cutlass.text.types.InputFormatConfiguration
> java.lang.NullPointerException:
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForNodeTest.testWritingThenReadingComponents
> Time elapsed: 0 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> java.lang.NoClassDefFoundError: Could not initialize class
> io.questdb.cutlass.text.types.InputFormatConfiguration
> java.lang.NullPointerException:
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-9811) QuestDB does not work on ARM
[
https://issues.apache.org/jira/browse/NIFI-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran resolved NIFI-9811.
---
Resolution: Fixed
Nothing to do here, as upgrading the quested dep version recently solved this
> QuestDB does not work on ARM
>
>
> Key: NIFI-9811
> URL: https://issues.apache.org/jira/browse/NIFI-9811
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Priority: Major
>
> Judging from this open issue, it does not appear they will be adding support:
> https://github.com/questdb/questdb/issues/569
> so for ARM, we will need to exclude this or find an alternative.
> Here is test failure output showing the runtime issues:
> {noformat}
> [INFO] Running
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest
> [ERROR] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.026
> s <<< FAILURE! - in
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest.testReadingEmptyRepository
> Time elapsed: 0.025 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> io.questdb.log.LogError: Error creating log writer
> java.lang.NullPointerException:
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest.testWritingThenReadingComponents
> Time elapsed: 0.001 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> java.lang.NoClassDefFoundError: Could not initialize class
> io.questdb.cutlass.text.types.InputFormatConfiguration
> java.lang.NullPointerException:
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest.testReadingLimitedByPreferredDataPoints
> Time elapsed: 0 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> java.lang.NoClassDefFoundError: Could not initialize class
> io.questdb.cutlass.text.types.InputFormatConfiguration
> java.lang.NullPointerException:
> [INFO] Running
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForNodeTest
> [ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 1, Time elapsed: 0 s
> <<< FAILURE! - in
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForNodeTest
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForNodeTest.testReadingEmptyRepository
> Time elapsed: 0 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> java.lang.NoClassDefFoundError: Could not initialize class
> io.questdb.cutlass.text.types.InputFormatConfiguration
> java.lang.NullPointerException:
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForNodeTest.testWritingThenReadingComponents
> Time elapsed: 0 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> java.lang.NoClassDefFoundError: Could not initialize class
> io.questdb.cutlass.text.types.InputFormatConfiguration
> java.lang.NullPointerException:
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-9809) Disable Kudu Tests on arm64 platforms
[
https://issues.apache.org/jira/browse/NIFI-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9809:
--
Status: Patch Available (was: Open)
> Disable Kudu Tests on arm64 platforms
> -
>
> Key: NIFI-9809
> URL: https://issues.apache.org/jira/browse/NIFI-9809
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The kudu-binary artifact is not available for aarch64 (arm64) platforms:
> {noformat}
> Could not resolve dependencies for project
> org.apache.nifi:nifi-kudu-controller-service:jar:1.17.0-SNAPSHOT:
> Could not transfer artifact
> org.apache.kudu:kudu-binary:jar:osx-aarch_64:1.16.0
> {noformat}
> AFAICT, we only use this dependency in test code. so excluding those tests
> from compiling / running when on those platforms should fix the kudu bundle
> build when running on that chip architecture.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-9811) QuestDB does not work on ARM
[
https://issues.apache.org/jira/browse/NIFI-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565171#comment-17565171
]
Kevin Doran commented on NIFI-9811:
---
Update, it looks like QuestDB v6 re-introduced arm support:
https://github.com/questdb/questdb/issues/569#issuecomment-1114570465
QuestDB was recently updated to version 6.3 as part of Java 17 compatibility
changes, so there may actually be nothing left to do for this ticket other than
testing to see if it is resolved.
> QuestDB does not work on ARM
>
>
> Key: NIFI-9811
> URL: https://issues.apache.org/jira/browse/NIFI-9811
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Priority: Major
>
> Judging from this open issue, it does not appear they will be adding support:
> https://github.com/questdb/questdb/issues/569
> so for ARM, we will need to exclude this or find an alternative.
> Here is test failure output showing the runtime issues:
> {noformat}
> [INFO] Running
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest
> [ERROR] Tests run: 3, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.026
> s <<< FAILURE! - in
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest.testReadingEmptyRepository
> Time elapsed: 0.025 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> io.questdb.log.LogError: Error creating log writer
> java.lang.NullPointerException:
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest.testWritingThenReadingComponents
> Time elapsed: 0.001 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> java.lang.NoClassDefFoundError: Could not initialize class
> io.questdb.cutlass.text.types.InputFormatConfiguration
> java.lang.NullPointerException:
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForComponentsTest.testReadingLimitedByPreferredDataPoints
> Time elapsed: 0 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> java.lang.NoClassDefFoundError: Could not initialize class
> io.questdb.cutlass.text.types.InputFormatConfiguration
> java.lang.NullPointerException:
> [INFO] Running
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForNodeTest
> [ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 1, Time elapsed: 0 s
> <<< FAILURE! - in
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForNodeTest
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForNodeTest.testReadingEmptyRepository
> Time elapsed: 0 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> java.lang.NoClassDefFoundError: Could not initialize class
> io.questdb.cutlass.text.types.InputFormatConfiguration
> java.lang.NullPointerException:
> [ERROR]
> org.apache.nifi.controller.status.history.EmbeddedQuestDbStatusHistoryRepositoryForNodeTest.testWritingThenReadingComponents
> Time elapsed: 0 s <<< FAILURE!
> org.opentest4j.MultipleFailuresError:
> Multiple Failures (2 failures)
> java.lang.NoClassDefFoundError: Could not initialize class
> io.questdb.cutlass.text.types.InputFormatConfiguration
> java.lang.NullPointerException:
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (NIFI-9809) Disable Kudu Tests on arm64 platforms
[
https://issues.apache.org/jira/browse/NIFI-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran reassigned NIFI-9809:
-
Assignee: Kevin Doran
> Disable Kudu Tests on arm64 platforms
> -
>
> Key: NIFI-9809
> URL: https://issues.apache.org/jira/browse/NIFI-9809
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
>
> The kudu-binary artifact is not available for aarch64 (arm64) platforms:
> {noformat}
> Could not resolve dependencies for project
> org.apache.nifi:nifi-kudu-controller-service:jar:1.17.0-SNAPSHOT:
> Could not transfer artifact
> org.apache.kudu:kudu-binary:jar:osx-aarch_64:1.16.0
> {noformat}
> AFAICT, we only use this dependency in test code. so excluding those tests
> from compiling / running when on those platforms should fix the kudu bundle
> build when running on that chip architecture.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-9809) Disable Kudu Tests on arm64 platforms
[
https://issues.apache.org/jira/browse/NIFI-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9809:
--
Description:
The kudu-binary artifact is not available for aarch64 (arm64) platforms:
{noformat}
Could not resolve dependencies for project
org.apache.nifi:nifi-kudu-controller-service:jar:1.17.0-SNAPSHOT:
Could not transfer artifact org.apache.kudu:kudu-binary:jar:osx-aarch_64:1.16.0
{noformat}
AFAICT, we only use this dependency in test code. so excluding those tests from
compiling / running when on those platforms should fix the kudu bundle build
when running on that chip architecture.
was:
The kudu-binary artifact is not available for aarch64 (arm64) platforms:
{noformat}
We only use this dependency in test code. so excluding those tests from
compiling / running when on those platforms should fix the kudu bundle build
when running on that chip architecture.
{noformat}
Could not resolve dependencies for project
org.apache.nifi:nifi-kudu-controller-service:jar:1.17.0-SNAPSHOT: Could not
transfer artifact org.apache.kudu:kudu-binary:jar:osx-aarch_64:1.16.0
> Disable Kudu Tests on arm64 platforms
> -
>
> Key: NIFI-9809
> URL: https://issues.apache.org/jira/browse/NIFI-9809
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Priority: Minor
>
> The kudu-binary artifact is not available for aarch64 (arm64) platforms:
> {noformat}
> Could not resolve dependencies for project
> org.apache.nifi:nifi-kudu-controller-service:jar:1.17.0-SNAPSHOT:
> Could not transfer artifact
> org.apache.kudu:kudu-binary:jar:osx-aarch_64:1.16.0
> {noformat}
> AFAICT, we only use this dependency in test code. so excluding those tests
> from compiling / running when on those platforms should fix the kudu bundle
> build when running on that chip architecture.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-9809) Disable Kudu Tests on arm64 platforms
[
https://issues.apache.org/jira/browse/NIFI-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9809:
--
Description:
The kudu-binary artifact is not available for aarch64 (arm64) platforms:
{noformat}
We only use this dependency in test code. so excluding those tests from
compiling / running when on those platforms should fix the kudu bundle build
when running on that chip architecture.
{noformat}
Could not resolve dependencies for project
org.apache.nifi:nifi-kudu-controller-service:jar:1.17.0-SNAPSHOT: Could not
transfer artifact org.apache.kudu:kudu-binary:jar:osx-aarch_64:1.16.0
was:For now, the nifi-kudu-bundle is excluded when building for arm because
the kudu dependencies are not available for arm platforms. This ticket is to
investigate what it would take to support kudu on NiFi on arm.
> Disable Kudu Tests on arm64 platforms
> -
>
> Key: NIFI-9809
> URL: https://issues.apache.org/jira/browse/NIFI-9809
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Priority: Minor
>
> The kudu-binary artifact is not available for aarch64 (arm64) platforms:
> {noformat}
> We only use this dependency in test code. so excluding those tests from
> compiling / running when on those platforms should fix the kudu bundle build
> when running on that chip architecture.
> {noformat}
> Could not resolve dependencies for project
> org.apache.nifi:nifi-kudu-controller-service:jar:1.17.0-SNAPSHOT: Could not
> transfer artifact org.apache.kudu:kudu-binary:jar:osx-aarch_64:1.16.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-9809) Disable Kudu Tests on arm64 platforms
[ https://issues.apache.org/jira/browse/NIFI-9809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-9809: -- Summary: Disable Kudu Tests on arm64 platforms (was: Support Kudu NAR on arm64 platforms) > Disable Kudu Tests on arm64 platforms > - > > Key: NIFI-9809 > URL: https://issues.apache.org/jira/browse/NIFI-9809 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Kevin Doran >Priority: Minor > > For now, the nifi-kudu-bundle is excluded when building for arm because the > kudu dependencies are not available for arm platforms. This ticket is to > investigate what it would take to support kudu on NiFi on arm. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10162) Improve InvokeHTTP Property Configuration
[
https://issues.apache.org/jira/browse/NIFI-10162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-10162:
---
Fix Version/s: 1.17.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Improve InvokeHTTP Property Configuration
> -
>
> Key: NIFI-10162
> URL: https://issues.apache.org/jira/browse/NIFI-10162
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> The {{InvokeHTTP}} Processor includes a number of required and optional
> properties that support a variety of use cases. The introduction of framework
> support for dependent properties provides the opportunity to streamline the
> number of properties visible in the default configuration. Among others,
> properties related to proxy configuration and authentication can have
> dependencies applied to indicate optional status. Adjusting property ordering
> to place required properties first would also make the configuration easier
> to follow.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-9810) Extract RocksDBFlowFileRepository to its own module and deprecate
[
https://issues.apache.org/jira/browse/NIFI-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17560621#comment-17560621
]
Kevin Doran commented on NIFI-9810:
---
After discussion with [~exceptionfactory] and [~joewitt], the new RocksDB NAR
will be excluded from the convenience assembly binary, so users of that
implementation will have to download and add the NAR when they upgrade to NiFi
>=1.17.0, with a plan to drop it as an optional extension entirely in NiFi .20
> Extract RocksDBFlowFileRepository to its own module and deprecate
> -
>
> Key: NIFI-9810
> URL: https://issues.apache.org/jira/browse/NIFI-9810
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> For arm64 / Apple M1 compatibility, RocksDB needs to be bumped to >=
> v6.29.4.1 (see below for runtime errors on an Apple Silicon M1 Mac with the
> current version).
> RocksDB is used only by the RocksDBFlowFileRepository implementation. After
> wider discussion with the community and who could help test and verify this
> change, we came to the conclusion it makes the most sense to focus
> maintenance efforts on the default FlowFileRepository implementation and
> deprecate the RocksDB variant.
> For now, we will bump the version of RocksDB for arm64 compatibility on
> macOS, but this ticket is also to extract it to its own module to isolate it,
> and also mark it as deprecated with an eye on dropping it in a future major
> version of NiFi.
> *MIGRATION GUIDANCE NOTE*
> Users of the {{RocksDBFlowFileRepository}} will have to download the new
> {{org.apache.nifi::nifi-rocksdb-nar::x.y.z}} and add it to the lib directory
> after upgrading past 1.16.3
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-9810) Extract RocksDBFlowFileRepository to its own module and deprecate
[
https://issues.apache.org/jira/browse/NIFI-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9810:
--
Description:
For arm64 / Apple M1 compatibility, RocksDB needs to be bumped to >= v6.29.4.1
(see below for runtime errors on an Apple Silicon M1 Mac with the current
version).
RocksDB is used only by the RocksDBFlowFileRepository implementation. After
wider discussion with the community and who could help test and verify this
change, we came to the conclusion it makes the most sense to focus maintenance
efforts on the default FlowFileRepository implementation and deprecate the
RocksDB variant.
For now, we will bump the version of RocksDB for arm64 compatibility on macOS,
but this ticket is also to extract it to its own module to isolate it, and also
mark it as deprecated with an eye on dropping it in a future major version of
NiFi.
*MIGRATION GUIDANCE NOTE*
Users of the {{RocksDBFlowFileRepository}} will have to download the new
{{org.apache.nifi::nifi-rocksdb-nar::x.y.z}} and add it to the lib directory
after upgrading past 1.16.3
was:
For arm64 / Apple M1 compatibility, RocksDB needs to be bumped to >= v6.29.4.1
(see below for runtime errors on an Apple Silicon M1 Mac with the current
version).
RocksDB is used only by the RocksDBFlowFileRepository implementation. After
wider discussion with the community and who could help test and verify this
change, we came to the conclusion it makes the most sense to focus maintenance
efforts on the default FlowFileRepository implementation and deprecate the
RocksDB variant.
For now, we will bump the version of RocksDB for arm64 compatibility on macOS,
but this ticket is also to extract it to its own module to isolate it, and also
mark it as deprecated with an eye on dropping it in a future major version of
NiFi.
*MIGRATION GUIDANCE NOTE*
Users of the {{RocksDBFlowFileRepository}} will have to download the new
{{org.apache.nifi::nifi-rocksdb-nar::x.y.z}} and add it to the lib directory
after upgrading past 1.16.3
{noformat}
[INFO] -< org.apache.nifi:nifi-rocksdb-utils >-
[INFO] Building nifi-rocksdb-utils 1.16.0-SNAPSHOT [35/642]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
nifi-rocksdb-utils ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
nifi-rocksdb-utils ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.7.0:process
(process-resource-bundles) @ nifi-rocksdb-utils ---
[INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
[INFO] Copying 3 resources from 1 bundle.
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
nifi-rocksdb-utils ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] skip non existing resourceDirectory
/Users/kdoran/dev/code/nifi/nifi-commons/nifi-rocksdb-utils/src/main/resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
nifi-rocksdb-utils ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources) @
nifi-rocksdb-utils ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
nifi-rocksdb-utils ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
nifi-rocksdb-utils ---
[INFO] Changes detected - recompiling the module!
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
nifi-rocksdb-utils ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.nifi.rocksdb.TestRocksDBMetronome
[ERROR] Tests run: 10, Failures: 2, Errors: 7, Skipped: 0, Time elapsed: 0.097
s <<< FAILURE! - in org.apache.nifi.rocksdb.TestRocksDBMetronome
[ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(Path)
Time elapsed: 0.058 s <<< ERROR!
java.lang.UnsatisfiedLinkError:
/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib:
dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib,
0x0001): tried:
'/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib'
(mach-o file, but is an incompatible architecture (have 'x86_64', need
'arm64e')),
[jira] [Updated] (NIFI-9810) Extract RocksDBFlowFileRepository to its own module and deprecate
[
https://issues.apache.org/jira/browse/NIFI-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9810:
--
Assignee: Kevin Doran
Status: Patch Available (was: Open)
> Extract RocksDBFlowFileRepository to its own module and deprecate
> -
>
> Key: NIFI-9810
> URL: https://issues.apache.org/jira/browse/NIFI-9810
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> For arm64 / Apple M1 compatibility, RocksDB needs to be bumped to >=
> v6.29.4.1 (see below for runtime errors on an Apple Silicon M1 Mac with the
> current version).
> RocksDB is used only by the RocksDBFlowFileRepository implementation. After
> wider discussion with the community and who could help test and verify this
> change, we came to the conclusion it makes the most sense to focus
> maintenance efforts on the default FlowFileRepository implementation and
> deprecate the RocksDB variant.
> For now, we will bump the version of RocksDB for arm64 compatibility on
> macOS, but this ticket is also to extract it to its own module to isolate it,
> and also mark it as deprecated with an eye on dropping it in a future major
> version of NiFi.
> *MIGRATION GUIDANCE NOTE*
> Users of the {{RocksDBFlowFileRepository}} will have to download the new
> {{org.apache.nifi::nifi-rocksdb-nar::x.y.z}} and add it to the lib directory
> after upgrading past 1.16.3
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-9810) Extract RocksDBFlowFileRepository to its own module and deprecate
[
https://issues.apache.org/jira/browse/NIFI-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9810:
--
Fix Version/s: 1.17.0
> Extract RocksDBFlowFileRepository to its own module and deprecate
> -
>
> Key: NIFI-9810
> URL: https://issues.apache.org/jira/browse/NIFI-9810
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Priority: Minor
> Fix For: 1.17.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> For arm64 / Apple M1 compatibility, RocksDB needs to be bumped to >=
> v6.29.4.1 (see below for runtime errors on an Apple Silicon M1 Mac with the
> current version).
> RocksDB is used only by the RocksDBFlowFileRepository implementation. After
> wider discussion with the community and who could help test and verify this
> change, we came to the conclusion it makes the most sense to focus
> maintenance efforts on the default FlowFileRepository implementation and
> deprecate the RocksDB variant.
> For now, we will bump the version of RocksDB for arm64 compatibility on
> macOS, but this ticket is also to extract it to its own module to isolate it,
> and also mark it as deprecated with an eye on dropping it in a future major
> version of NiFi.
> *MIGRATION GUIDANCE NOTE*
> Users of the {{RocksDBFlowFileRepository}} will have to download the new
> {{org.apache.nifi::nifi-rocksdb-nar::x.y.z}} and add it to the lib directory
> after upgrading past 1.16.3
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-9810) Extract RocksDBFlowFileRepository to its own module and deprecate
[
https://issues.apache.org/jira/browse/NIFI-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9810:
--
Description:
For arm64 / Apple M1 compatibility, RocksDB needs to be bumped to >= v6.29.4.1
(see below for runtime errors on an Apple Silicon M1 Mac with the current
version).
RocksDB is used only by the RocksDBFlowFileRepository implementation. After
wider discussion with the community and who could help test and verify this
change, we came to the conclusion it makes the most sense to focus maintenance
efforts on the default FlowFileRepository implementation and deprecate the
RocksDB variant.
For now, we will bump the version of RocksDB for arm64 compatibility on macOS,
but this ticket is also to extract it to its own module to isolate it, and also
mark it as deprecated with an eye on dropping it in a future major version of
NiFi.
*MIGRATION GUIDANCE NOTE*
Users of the {{RocksDBFlowFileRepository}} will have to download the new
{{org.apache.nifi::nifi-rocksdb-nar::x.y.z}} and add it to the lib directory
after upgrading past 1.16.3
{noformat}
[INFO] -< org.apache.nifi:nifi-rocksdb-utils >-
[INFO] Building nifi-rocksdb-utils 1.16.0-SNAPSHOT [35/642]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
nifi-rocksdb-utils ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
nifi-rocksdb-utils ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.7.0:process
(process-resource-bundles) @ nifi-rocksdb-utils ---
[INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
[INFO] Copying 3 resources from 1 bundle.
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
nifi-rocksdb-utils ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] skip non existing resourceDirectory
/Users/kdoran/dev/code/nifi/nifi-commons/nifi-rocksdb-utils/src/main/resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
nifi-rocksdb-utils ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources) @
nifi-rocksdb-utils ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
nifi-rocksdb-utils ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
nifi-rocksdb-utils ---
[INFO] Changes detected - recompiling the module!
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
nifi-rocksdb-utils ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.nifi.rocksdb.TestRocksDBMetronome
[ERROR] Tests run: 10, Failures: 2, Errors: 7, Skipped: 0, Time elapsed: 0.097
s <<< FAILURE! - in org.apache.nifi.rocksdb.TestRocksDBMetronome
[ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(Path)
Time elapsed: 0.058 s <<< ERROR!
java.lang.UnsatisfiedLinkError:
/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib:
dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib,
0x0001): tried:
'/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib'
(mach-o file, but is an incompatible architecture (have 'x86_64', need
'arm64e')), '/usr/lib/librocksdbjni1540031708884427750.jnilib' (no such file)
at
org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(TestRocksDBMetronome.java:170)
[ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(Path)
Time elapsed: 0.003 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
at
org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(TestRocksDBMetronome.java:267)
[ERROR]
org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(Path)
Time elapsed: 0.001 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
at
org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(TestRocksDBMetronome.java:299)
[ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testCounterIncrement(Path)
Time elapsed: 0.001 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class
[jira] [Updated] (NIFI-9810) Extract RocksDBFlowFileRepository to its own module and deprecate
[
https://issues.apache.org/jira/browse/NIFI-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9810:
--
Description:
For arm64 / Apple M1 compatibility, RocksDB needs to be bumped to >= v6.29.4.1
(see below for runtime errors on an Apple Silicon M1 Mac with the current
version).
RocksDB is used only by the RocksDBFlowFileRepository implementation. After
wider discussion with the community and who could help test and verify this
change, we came to the conclusion it makes the most sense to focus maintenance
efforts on the default FlowFileRepository implementation and deprecate the
RocksDB variant.
For now, we will bump the version of RocksDB for arm64 compatibility on macOS,
but this ticket is also to extract it to its own module to isolate it, and also
mark it as deprecated with an eye on dropping it in a future major version of
NiFi.
{noformat}
[INFO] -< org.apache.nifi:nifi-rocksdb-utils >-
[INFO] Building nifi-rocksdb-utils 1.16.0-SNAPSHOT [35/642]
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
nifi-rocksdb-utils ---
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
nifi-rocksdb-utils ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.7.0:process
(process-resource-bundles) @ nifi-rocksdb-utils ---
[INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
[INFO] Copying 3 resources from 1 bundle.
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
nifi-rocksdb-utils ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] skip non existing resourceDirectory
/Users/kdoran/dev/code/nifi/nifi-commons/nifi-rocksdb-utils/src/main/resources
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
nifi-rocksdb-utils ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources) @
nifi-rocksdb-utils ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Using 'UTF-8' encoding to copy filtered properties files.
[INFO] Copying 1 resource
[INFO] Copying 3 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
nifi-rocksdb-utils ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
nifi-rocksdb-utils ---
[INFO] Changes detected - recompiling the module!
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
nifi-rocksdb-utils ---
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
[INFO] Running org.apache.nifi.rocksdb.TestRocksDBMetronome
[ERROR] Tests run: 10, Failures: 2, Errors: 7, Skipped: 0, Time elapsed: 0.097
s <<< FAILURE! - in org.apache.nifi.rocksdb.TestRocksDBMetronome
[ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(Path)
Time elapsed: 0.058 s <<< ERROR!
java.lang.UnsatisfiedLinkError:
/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib:
dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib,
0x0001): tried:
'/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib'
(mach-o file, but is an incompatible architecture (have 'x86_64', need
'arm64e')), '/usr/lib/librocksdbjni1540031708884427750.jnilib' (no such file)
at
org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(TestRocksDBMetronome.java:170)
[ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(Path)
Time elapsed: 0.003 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
at
org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(TestRocksDBMetronome.java:267)
[ERROR]
org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(Path)
Time elapsed: 0.001 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
at
org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(TestRocksDBMetronome.java:299)
[ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testCounterIncrement(Path)
Time elapsed: 0.001 s <<< ERROR!
java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
at
org.apache.nifi.rocksdb.TestRocksDBMetronome.testCounterIncrement(TestRocksDBMetronome.java:247)
[ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testPutGetDelete(Path)
[jira] [Comment Edited] (NIFI-9810) Extract RocksDBFlowFileRepository to its own module and deprecate
[
https://issues.apache.org/jira/browse/NIFI-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17558233#comment-17558233
]
Kevin Doran edited comment on NIFI-9810 at 6/24/22 4:00 PM:
After discussing with [~markap14], RocksDB will be moved to its own module and
deprecated, with a plan to remove it in NiFi 2.0
was (Author: kdoran):
After discussing with [~markap14], RocksDB will be moved to its own NAR and
deprecated, with a plan to remove it in NiFi 2.0
> Extract RocksDBFlowFileRepository to its own module and deprecate
> -
>
> Key: NIFI-9810
> URL: https://issues.apache.org/jira/browse/NIFI-9810
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Priority: Minor
>
> {noformat}
> [INFO] -< org.apache.nifi:nifi-rocksdb-utils
> >-
> [INFO] Building nifi-rocksdb-utils 1.16.0-SNAPSHOT
> [35/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-rocksdb-utils ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-rocksdb-utils ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-rocksdb-utils ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-rocksdb-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] skip non existing resourceDirectory
> /Users/kdoran/dev/code/nifi/nifi-commons/nifi-rocksdb-utils/src/main/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-rocksdb-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-rocksdb-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-rocksdb-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-rocksdb-utils ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-rocksdb-utils ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.rocksdb.TestRocksDBMetronome
> [ERROR] Tests run: 10, Failures: 2, Errors: 7, Skipped: 0, Time elapsed:
> 0.097 s <<< FAILURE! - in org.apache.nifi.rocksdb.TestRocksDBMetronome
> [ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(Path)
> Time elapsed: 0.058 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib:
>
> dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib,
> 0x0001): tried:
> '/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib'
> (mach-o file, but is an incompatible architecture (have 'x86_64', need
> 'arm64e')), '/usr/lib/librocksdbjni1540031708884427750.jnilib' (no such file)
> at
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(TestRocksDBMetronome.java:170)
> [ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(Path)
> Time elapsed: 0.003 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
> at
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(TestRocksDBMetronome.java:267)
> [ERROR]
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(Path)
> Time elapsed: 0.001 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
> at
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(TestRocksDBMetronome.java:299)
> [ERROR]
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testCounterIncrement(Path) Time
> elapsed: 0.001 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
> at
>
[jira] [Updated] (NIFI-9810) Extract RocksDBFlowFileRepository to its own module and deprecate
[
https://issues.apache.org/jira/browse/NIFI-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-9810:
--
Summary: Extract RocksDBFlowFileRepository to its own module and deprecate
(was: RocksDB does not work on ARM)
> Extract RocksDBFlowFileRepository to its own module and deprecate
> -
>
> Key: NIFI-9810
> URL: https://issues.apache.org/jira/browse/NIFI-9810
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Priority: Minor
>
> {noformat}
> [INFO] -< org.apache.nifi:nifi-rocksdb-utils
> >-
> [INFO] Building nifi-rocksdb-utils 1.16.0-SNAPSHOT
> [35/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-rocksdb-utils ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-rocksdb-utils ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-rocksdb-utils ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-rocksdb-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] skip non existing resourceDirectory
> /Users/kdoran/dev/code/nifi/nifi-commons/nifi-rocksdb-utils/src/main/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-rocksdb-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-rocksdb-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-rocksdb-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-rocksdb-utils ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-rocksdb-utils ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.rocksdb.TestRocksDBMetronome
> [ERROR] Tests run: 10, Failures: 2, Errors: 7, Skipped: 0, Time elapsed:
> 0.097 s <<< FAILURE! - in org.apache.nifi.rocksdb.TestRocksDBMetronome
> [ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(Path)
> Time elapsed: 0.058 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib:
>
> dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib,
> 0x0001): tried:
> '/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib'
> (mach-o file, but is an incompatible architecture (have 'x86_64', need
> 'arm64e')), '/usr/lib/librocksdbjni1540031708884427750.jnilib' (no such file)
> at
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(TestRocksDBMetronome.java:170)
> [ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(Path)
> Time elapsed: 0.003 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
> at
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(TestRocksDBMetronome.java:267)
> [ERROR]
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(Path)
> Time elapsed: 0.001 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
> at
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(TestRocksDBMetronome.java:299)
> [ERROR]
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testCounterIncrement(Path) Time
> elapsed: 0.001 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
> at
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testCounterIncrement(TestRocksDBMetronome.java:247)
> [ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testPutGetDelete(Path)
> Time elapsed: 0.001 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class
[jira] [Commented] (NIFI-9810) RocksDB does not work on ARM
[
https://issues.apache.org/jira/browse/NIFI-9810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17558233#comment-17558233
]
Kevin Doran commented on NIFI-9810:
---
After discussing with [~markap14], RocksDB will be moved to its own NAR and
deprecated, with a plan to remove it in NiFi 2.0
> RocksDB does not work on ARM
>
>
> Key: NIFI-9810
> URL: https://issues.apache.org/jira/browse/NIFI-9810
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Kevin Doran
>Priority: Minor
>
> {noformat}
> [INFO] -< org.apache.nifi:nifi-rocksdb-utils
> >-
> [INFO] Building nifi-rocksdb-utils 1.16.0-SNAPSHOT
> [35/642]
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-maven-version) @
> nifi-rocksdb-utils ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce-java-version) @
> nifi-rocksdb-utils ---
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.7.0:process
> (process-resource-bundles) @ nifi-rocksdb-utils ---
> [INFO] Preparing remote bundle org.apache:apache-jar-resource-bundle:1.4
> [INFO] Copying 3 resources from 1 bundle.
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:resources (default-resources) @
> nifi-rocksdb-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] skip non existing resourceDirectory
> /Users/kdoran/dev/code/nifi/nifi-commons/nifi-rocksdb-utils/src/main/resources
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:compile (default-compile) @
> nifi-rocksdb-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-resources-plugin:3.2.0:testResources (default-testResources)
> @ nifi-rocksdb-utils ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Using 'UTF-8' encoding to copy filtered properties files.
> [INFO] Copying 1 resource
> [INFO] Copying 3 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (default-testCompile) @
> nifi-rocksdb-utils ---
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-compiler-plugin:3.9.0:testCompile (groovy-tests) @
> nifi-rocksdb-utils ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Nothing to compile - all classes are up to date
> [INFO]
> [INFO] --- maven-surefire-plugin:3.0.0-M5:test (default-test) @
> nifi-rocksdb-utils ---
> [INFO]
> [INFO] ---
> [INFO] T E S T S
> [INFO] ---
> [INFO] Running org.apache.nifi.rocksdb.TestRocksDBMetronome
> [ERROR] Tests run: 10, Failures: 2, Errors: 7, Skipped: 0, Time elapsed:
> 0.097 s <<< FAILURE! - in org.apache.nifi.rocksdb.TestRocksDBMetronome
> [ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(Path)
> Time elapsed: 0.058 s <<< ERROR!
> java.lang.UnsatisfiedLinkError:
> /private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib:
>
> dlopen(/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib,
> 0x0001): tried:
> '/private/var/folders/dj/1c85sd0d6dvcp1fltmwr5nl4gn/T/librocksdbjni1540031708884427750.jnilib'
> (mach-o file, but is an incompatible architecture (have 'x86_64', need
> 'arm64e')), '/usr/lib/librocksdbjni1540031708884427750.jnilib' (no such file)
> at
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testColumnFamilies(TestRocksDBMetronome.java:170)
> [ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(Path)
> Time elapsed: 0.003 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
> at
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSync(TestRocksDBMetronome.java:267)
> [ERROR]
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(Path)
> Time elapsed: 0.001 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
> at
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testWaitForSyncWithValue(TestRocksDBMetronome.java:299)
> [ERROR]
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testCounterIncrement(Path) Time
> elapsed: 0.001 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
> at
> org.apache.nifi.rocksdb.TestRocksDBMetronome.testCounterIncrement(TestRocksDBMetronome.java:247)
> [ERROR] org.apache.nifi.rocksdb.TestRocksDBMetronome.testPutGetDelete(Path)
> Time elapsed: 0.001 s <<< ERROR!
> java.lang.NoClassDefFoundError: Could not initialize class org.rocksdb.RocksDB
> at
>
[jira] [Updated] (NIFI-10155) Bump NiFi NAR Maven Plugin version to 1.3.4
[ https://issues.apache.org/jira/browse/NIFI-10155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran updated NIFI-10155: --- Status: Patch Available (was: In Progress) > Bump NiFi NAR Maven Plugin version to 1.3.4 > --- > > Key: NIFI-10155 > URL: https://issues.apache.org/jira/browse/NIFI-10155 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Major > Fix For: 1.17.0 > > Time Spent: 10m > Remaining Estimate: 0h > > NiFi NAR Maven Plugin version 1.3.4 was released and has propagated to all > indexed central repos. This ticket is to update NiFi to use the newest > version of this plugin. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (NIFI-10155) Bump NiFi NAR Maven Plugin version to 1.3.4
Kevin Doran created NIFI-10155: -- Summary: Bump NiFi NAR Maven Plugin version to 1.3.4 Key: NIFI-10155 URL: https://issues.apache.org/jira/browse/NIFI-10155 Project: Apache NiFi Issue Type: Improvement Reporter: Kevin Doran Assignee: Kevin Doran Fix For: 1.17.0 NiFi NAR Maven Plugin version 1.3.4 was released and has propagated to all indexed central repos. This ticket is to update NiFi to use the newest version of this plugin. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (NIFI-10147) Remove Support for Java 8
[ https://issues.apache.org/jira/browse/NIFI-10147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17557038#comment-17557038 ] Kevin Doran commented on NIFI-10147: Do we want to make a 2.0 development branch in the central code repository? I'm thinking it would be a place that experimental work could begin, to be continually rebased on main, until we are ready to release 2.0, at which point we could push the 2.0 development branch to main. Would this be helpful to start making progress? Would rebases be too complicated to sustain this work? > Remove Support for Java 8 > - > > Key: NIFI-10147 > URL: https://issues.apache.org/jira/browse/NIFI-10147 > Project: Apache NiFi > Issue Type: Epic > Components: Core Framework, MiNiFi, NiFi Registry, NiFi Stateless >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Although multiple vendors have planned extended support for Java 8, a number > of projects are in the process of deprecating and removing support for Java > 8. These projects include the following: > - [Jetty 9.4|https://github.com/eclipse/jetty.project/issues/7958] > - [Spring > 5|https://spring.io/blog/2021/09/02/a-java-17-and-jakarta-ee-9-baseline-for-spring-framework-6] > - [OpenSAML 3|https://shibboleth.atlassian.net/wiki/spaces/OSAML/overview] > Apache NiFi should also remove support for Java 8 in order to maintain active > support for various components. > Removing support for Java 8 requires a new major version release and will > also require several build configuration changes including the following: > - Updating Maven source and compiler settings > - Updating minimum Java build version > - Removing optional Maven build profiles > - Updating GitHub workflows > Initial discussion on a migration strategy included a tentative target of the > end of calendar year 2022. > Implementation should not proceed until after a minor release of Apache NiFi > 1.17.0. > Mailing list discussion: > [https://lists.apache.org/thread/mm1xf3b9nvrcgytb92oy3swvvc45fl34] -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Resolved] (NIFI-10131) Release Manager - Release NAR Maven Plugin 1.3.4
[ https://issues.apache.org/jira/browse/NIFI-10131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran resolved NIFI-10131. Resolution: Done > Release Manager - Release NAR Maven Plugin 1.3.4 > > > Key: NIFI-10131 > URL: https://issues.apache.org/jira/browse/NIFI-10131 > Project: Apache NiFi > Issue Type: Task >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Major > Fix For: nifi-nar-maven-plugin-1.3.4 > > Time Spent: 10m > Remaining Estimate: 0h > > Perform release manage activities for NAR Maven Plugin 1.3.4 release -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (NIFI-10131) Release Manager - Release NAR Maven Plugin 1.3.4
Kevin Doran created NIFI-10131: -- Summary: Release Manager - Release NAR Maven Plugin 1.3.4 Key: NIFI-10131 URL: https://issues.apache.org/jira/browse/NIFI-10131 Project: Apache NiFi Issue Type: Task Reporter: Kevin Doran Assignee: Kevin Doran Fix For: nifi-nar-maven-plugin-1.3.4 Perform release manage activities for NAR Maven Plugin 1.3.4 release -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (NIFI-10011) Extension manifest does not include all provided APIs
[
https://issues.apache.org/jira/browse/NIFI-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-10011:
---
Priority: Major (was: Minor)
> Extension manifest does not include all provided APIs
> -
>
> Key: NIFI-10011
> URL: https://issues.apache.org/jira/browse/NIFI-10011
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: nifi-nar-maven-plugin-1.3.3
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Major
> Fix For: nifi-nar-maven-plugin-1.3.4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The NAR Maven plugin attempts to determine the APIs that are implemented by a
> controller service and pass them to the documentation writer. The current
> code only looks for interfaces directly on the extension class, but the
> extension class may extend from a base class that implements the actual API,
> and in this case it is missed.
> Examples of services that don't have the correct provided APIs in their
> extension manifest:
> {code:java}
> org.apache.nifi.rules.handlers.AlertHandler
> org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer
> org.apache.nifi.kerberos.KerberosPasswordUserService
> org.apache.nifi.rules.handlers.ActionHandlerLookup
> org.apache.nifi.rules.handlers.ExpressionHandler
> org.apache.nifi.hazelcast.services.cachemanager.EmbeddedHazelcastCacheManager
> org.apache.nifi.snowflake.service.SnowflakeComputingConnectionPool
> org.apache.nifi.hazelcast.services.cachemanager.ExternalHazelcastCacheManager
> org.apache.nifi.rules.handlers.LogHandler
> org.apache.nifi.distributed.cache.server.DistributedSetCacheServer
> org.apache.nifi.lookup.XMLFileLookupService
> org.apache.nifi.lookup.PropertiesFileLookupService
> org.apache.nifi.rules.handlers.RecordSinkHandler {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Resolved] (NIFI-9857) make output reproducible
[ https://issues.apache.org/jira/browse/NIFI-9857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Doran resolved NIFI-9857. --- Resolution: Fixed > make output reproducible > > > Key: NIFI-9857 > URL: https://issues.apache.org/jira/browse/NIFI-9857 > Project: Apache NiFi > Issue Type: Improvement > Components: Tools and Build >Affects Versions: nifi-nar-maven-plugin-1.3.3 >Reporter: Herve Boutemy >Priority: Major > Fix For: nifi-nar-maven-plugin-1.3.4 > > Time Spent: 0.5h > Remaining Estimate: 0h > > current output is not reproducible: see the end of > https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/org/apache/nifi/nifi-1.16.0.diffoscope -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (NIFI-10011) Extension manifest does not include all provided APIs
[
https://issues.apache.org/jira/browse/NIFI-10011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Doran updated NIFI-10011:
---
Fix Version/s: nifi-nar-maven-plugin-1.3.4
Resolution: Resolved
Status: Resolved (was: Patch Available)
> Extension manifest does not include all provided APIs
> -
>
> Key: NIFI-10011
> URL: https://issues.apache.org/jira/browse/NIFI-10011
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: nifi-nar-maven-plugin-1.3.3
>Reporter: Bryan Bende
>Assignee: Bryan Bende
>Priority: Minor
> Fix For: nifi-nar-maven-plugin-1.3.4
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The NAR Maven plugin attempts to determine the APIs that are implemented by a
> controller service and pass them to the documentation writer. The current
> code only looks for interfaces directly on the extension class, but the
> extension class may extend from a base class that implements the actual API,
> and in this case it is missed.
> Examples of services that don't have the correct provided APIs in their
> extension manifest:
> {code:java}
> org.apache.nifi.rules.handlers.AlertHandler
> org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer
> org.apache.nifi.kerberos.KerberosPasswordUserService
> org.apache.nifi.rules.handlers.ActionHandlerLookup
> org.apache.nifi.rules.handlers.ExpressionHandler
> org.apache.nifi.hazelcast.services.cachemanager.EmbeddedHazelcastCacheManager
> org.apache.nifi.snowflake.service.SnowflakeComputingConnectionPool
> org.apache.nifi.hazelcast.services.cachemanager.ExternalHazelcastCacheManager
> org.apache.nifi.rules.handlers.LogHandler
> org.apache.nifi.distributed.cache.server.DistributedSetCacheServer
> org.apache.nifi.lookup.XMLFileLookupService
> org.apache.nifi.lookup.PropertiesFileLookupService
> org.apache.nifi.rules.handlers.RecordSinkHandler {code}
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
