[jira] [Assigned] (MINIFI-553) Fix timeout-based tests in StatusLoggerTest
[ https://issues.apache.org/jira/browse/MINIFI-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess reassigned MINIFI-553: --- Assignee: Matt Burgess > Fix timeout-based tests in StatusLoggerTest > --- > > Key: MINIFI-553 > URL: https://issues.apache.org/jira/browse/MINIFI-553 > Project: Apache NiFi MiNiFi > Issue Type: Test > Components: Testing >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > > Github Actions is intermittently failing due to timeout issues in > StatusLoggerTest. The tests should be refactored to ensure no timeout issues > occur. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MINIFI-553) Fix timeout-based tests in StatusLoggerTest
Matt Burgess created MINIFI-553: --- Summary: Fix timeout-based tests in StatusLoggerTest Key: MINIFI-553 URL: https://issues.apache.org/jira/browse/MINIFI-553 Project: Apache NiFi MiNiFi Issue Type: Test Components: Testing Reporter: Matt Burgess Github Actions is intermittently failing due to timeout issues in StatusLoggerTest. The tests should be refactored to ensure no timeout issues occur. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFI-476) Release 0.6.0
[ https://issues.apache.org/jira/browse/MINIFI-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess resolved MINIFI-476. - Resolution: Won't Do OBE by MINIFI-422, next release will be 1.14.0 and remain in lockstep with NiFi > Release 0.6.0 > - > > Key: MINIFI-476 > URL: https://issues.apache.org/jira/browse/MINIFI-476 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Aldrin Piri >Priority: Major > > With the upcoming NiFi 1.8.0 release and some of the fixes that went into the > current state, we should perform a release of these once the NiFi libraries > on which we depend are available. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFI-545) Classes are not loading, during the build on 64bit RISC-V board
[ https://issues.apache.org/jira/browse/MINIFI-545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess resolved MINIFI-545. - Resolution: Duplicate Resolving as duplicate of MINIFI-546 (Java 11 support) > Classes are not loading, during the build on 64bit RISC-V board > --- > > Key: MINIFI-545 > URL: https://issues.apache.org/jira/browse/MINIFI-545 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Agent Configuration/Installation, Build >Affects Versions: 1.0.0 > Environment: $ java -version > openjdk version "11.0.8" 2020-07-14 > OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.8+10-202007292333) > Eclipse OpenJ9 VM AdoptOpenJDK (build master-dc7cbe4bd, JRE 11 Linux > riscv-64-Bit Compressed References 20200729_78 (JIT disabled, AOT disabled) > OpenJ9 - dc7cbe4bd > OMR - 1c0299f20 > JCL - 94b9d6d2c6 based on jdk-11.0.8+10) > $ javac -version > javac 11.0.8 > $ cat /proc/cpuinfo && uname -a && cat /etc/*release* > processor : 0 > hart : 1 > isa : rv64imafdc > mmu : sv39 > uarch : sifive,rocket0 > processor : 1 > hart : 2 > isa : rv64imafdc > mmu : sv39 > uarch : sifive,rocket0 > processor : 2 > hart : 3 > isa : rv64imafdc > mmu : sv39 > uarch : sifive,rocket0 > processor : 3 > hart : 4 > isa : rv64imafdc > mmu : sv39 > uarch : sifive,rocket0 > Linux test-gdams-debian10-riscv64-1.adoptopenjdk.net > 5.0.0-rc1-56210-g0a657e0d72f0 #1 SMP Fri May 15 18:05:26 EDT 2020 riscv64 > GNU/Linux > PRETTY_NAME="Debian GNU/Linux bullseye/sid" >Reporter: Ivan Serdyuk >Priority: Trivial > Labels: build > > Here is the brief summary: > ??[ERROR] bootstrap class path not set in conjunction with -source 8?? > ??/home/ivan/nifi-minifi/minifi-toolkit/minifi-toolkit-configuration/src/main/java/org/apache/nifi/minifi/toolkit/configuration/ConfigMain.java:[36,21] > error: package javax.xml.bind does not exist?? > ??[ERROR] > /home/ivan/nifi-minifi/minifi-toolkit/minifi-toolkit-configuration/src/main/java/org/apache/nifi/minifi/toolkit/configuration/ConfigMain.java:[37,21] > error: package javax.xml.bind does not exist?? > ??[ERROR] > /home/ivan/nifi-minifi/minifi-toolkit/minifi-toolkit-configuration/src/main/java/org/apache/nifi/minifi/toolkit/configuration/ConfigMain.java:[132,84] > error: cannot find symbol?? > ??[ERROR] > /home/ivan/nifi-minifi/minifi-toolkit/minifi-toolkit-configuration/src/main/java/org/apache/nifi/minifi/toolkit/configuration/ConfigMain.java:[134,52] > error: cannot find symbol?? > ??[ERROR] symbol: variable JAXBContext?? > ?? location: class ConfigMain?? > ??/home/ivan/nifi-minifi/minifi-toolkit/minifi-toolkit-configuration/src/main/java/org/apache/nifi/minifi/toolkit/configuration/ConfigMain.java:[259,21] > error: cannot find symbol?? > ??[INFO] 5 errors?? > > [https://gist.github.com/advancedwebdeveloper/36d8baa78c1a9bcd0b83040eb2f92f12|Here] > is the detailed coverage. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (MINIFI-494) Update NiFi dependency to 1.9.0
[ https://issues.apache.org/jira/browse/MINIFI-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess reassigned MINIFI-494: --- Assignee: Matt Burgess > Update NiFi dependency to 1.9.0 > --- > > Key: MINIFI-494 > URL: https://issues.apache.org/jira/browse/MINIFI-494 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Build >Reporter: Jeffrey T. Zemerick >Assignee: Matt Burgess >Priority: Major > > Update NiFi dependency to 1.9.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFI-481) Update to use new handling of ExtensionManager
[ https://issues.apache.org/jira/browse/MINIFI-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess resolved MINIFI-481. - Resolution: Fixed > Update to use new handling of ExtensionManager > -- > > Key: MINIFI-481 > URL: https://issues.apache.org/jira/browse/MINIFI-481 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Core Framework >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > > ExtensionManager was refactored to aid in extension registry efforts and has > migrated away from the static instance previously used. The two commits of > most interest are > https://github.com/apache/nifi/commit/fdd8cdbb31a8977967d4437ba9a09104bf6cf450 > and > https://github.com/apache/nifi/commit/931bb0bc3b1c0205b260261ce9730af87204e115 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-422) Incorporate MiNiFi Java functionality as a specialized assembly of NiFI
[ https://issues.apache.org/jira/browse/MINIFI-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-422: Fix Version/s: 1.14.0 > Incorporate MiNiFi Java functionality as a specialized assembly of NiFI > > > Key: MINIFI-422 > URL: https://issues.apache.org/jira/browse/MINIFI-422 > Project: Apache NiFi MiNiFi > Issue Type: Task >Reporter: Aldrin Piri >Assignee: Matt Burgess >Priority: Major > Fix For: 1.14.0 > > Time Spent: 5h 10m > Remaining Estimate: 0h > > At its core the Java implementation of MiNiFi has largely been a core body of > NiFi core libraries in a separate assembly with some additional extension > points, namely those of configuration (via YAML) and configuration change > listeners. > Due to working with some of the internals of NiFi that are not exactly meant > for external consumption, there has been a certain impedance with each > successive release to make use of the latest and greatest. > This ticket is to investigate and consider the incorporation of MiNiFi Java > into the NiFi code base in a manner as highlighted above, extending/adapting > the core libraries, providing some additional extension points, and then > generating a custom assembly. > The idea is that in lieu of duplicating bits of code and providing > workarounds around some of the internal APIs we can have a more streamlined > build and keep these items in lockstep with the core NiFi libraries being > more aware of changes that MiNiFi is inherently dependent upon. > To our users, there should be little perceptible change. The core means of > interaction should remain while providing a similar footprint. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFI-494) Update NiFi dependency to 1.9.0
[ https://issues.apache.org/jira/browse/MINIFI-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess resolved MINIFI-494. - Resolution: Fixed Overcome By Events (MINIFI-422 integrates MiNiFi Java with NiFi so the versions are in lockstep) > Update NiFi dependency to 1.9.0 > --- > > Key: MINIFI-494 > URL: https://issues.apache.org/jira/browse/MINIFI-494 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Build >Reporter: Jeffrey T. Zemerick >Assignee: Matt Burgess >Priority: Major > > Update NiFi dependency to 1.9.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-494) Update NiFi dependency to 1.9.0
[ https://issues.apache.org/jira/browse/MINIFI-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-494: Affects Version/s: (was: 0.6.0) > Update NiFi dependency to 1.9.0 > --- > > Key: MINIFI-494 > URL: https://issues.apache.org/jira/browse/MINIFI-494 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Build >Reporter: Jeffrey T. Zemerick >Priority: Major > > Update NiFi dependency to 1.9.0. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-498) C2 Server Error - Too Many Open Files
[ https://issues.apache.org/jira/browse/MINIFI-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-498: Fix Version/s: (was: 0.6.0) 1.14.0 > C2 Server Error - Too Many Open Files > - > > Key: MINIFI-498 > URL: https://issues.apache.org/jira/browse/MINIFI-498 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Command and Control >Affects Versions: 0.5.0 > Environment: OS: Amazon Linux 2 (4.14.77-86.82.amzn2.x86_64) > Java: 1.8.0_191-b12 > ulimits: > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 31769 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 5 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 8192 > cpu time (seconds, -t) unlimited > max user processes (-u) 1 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited >Reporter: Michael >Assignee: Corinne Jukes >Priority: Blocker > Fix For: 1.14.0 > > > After several days of running C2 the errors are being logged about having > "Too Many Open Files". At this point, C2 is not responsive to clients trying > to check for new configurations. > _33e79e: Too many open files_ > _Apr 29 14:33:22 ec2.internal c2.sh[20851]: Caused by: > java.nio.file.FileSystemException: > /opt/minifi-c2/./files/5233730D-AC58-4853-9C0E-273D0E_ > > Running _lsof_ shows an increasingly larger number of open files. Our MiNiFi > instances are checking for new files every few seconds (probably too short), > but it seems like maybe some file handles are not being cleaned up. > Restarting C2 clears up this condition and C2 becomes responsive again. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-482) MiNiFi handle multiple NiFi urls in RPG
[ https://issues.apache.org/jira/browse/MINIFI-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-482: Fix Version/s: (was: 0.6.0) 1.14.0 > MiNiFi handle multiple NiFi urls in RPG > --- > > Key: MINIFI-482 > URL: https://issues.apache.org/jira/browse/MINIFI-482 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Neha Bathra >Assignee: Aldrin Piri >Priority: Critical > Fix For: 1.14.0 > > > For an RPG, when multiple comma separated nifi urls are configured, only the > first url is considered for data flow. In case, the first url is down, it > should be tried on the other nodes. Currently, the data flow gets stuck when > the first nifi url is down. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-515) Make use of new location for commons-daemon
[ https://issues.apache.org/jira/browse/MINIFI-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-515: Fix Version/s: (was: 0.6.0) 1.14.0 > Make use of new location for commons-daemon > --- > > Key: MINIFI-515 > URL: https://issues.apache.org/jira/browse/MINIFI-515 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Related to MINIFI-508 and MINIFI-514. Plan to make use of a mirrored > repository to have a consistent location and not make builds so fragile when > releases occur. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[nifi] branch main updated (a0655bf -> 93dcf25)
This is an automated email from the ASF dual-hosted git repository. mattyb149 pushed a change to branch main in repository https://gitbox.apache.org/repos/asf/nifi.git. from a0655bf MINIFI-422: Incorporate MiNiFi Java into NiFi add 93dcf25 MINIFI-552: Fix new SSL SAN Behaviour from new Jetty Version No new revisions were added by this update. Summary of changes: .../java/org/apache/nifi/minifi/c2/api/properties/C2Properties.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
[jira] [Updated] (MINIFI-514) Update commons-daemon to 1.2.1
[ https://issues.apache.org/jira/browse/MINIFI-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-514: Fix Version/s: (was: 0.6.0) 1.14.0 > Update commons-daemon to 1.2.1 > -- > > Key: MINIFI-514 > URL: https://issues.apache.org/jira/browse/MINIFI-514 > Project: Apache NiFi MiNiFi > Issue Type: Task >Affects Versions: 0.5.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Commons-daemon had a bugfix release and we will need to perform another > update as the prior version has rolled off many mirrors. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-504) Upgrade commons-deamon to 1.2.0 to make build green again
[
https://issues.apache.org/jira/browse/MINIFI-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated MINIFI-504:
Fix Version/s: (was: 0.6.0)
1.14.0
> Upgrade commons-deamon to 1.2.0 to make build green again
> -
>
> Key: MINIFI-504
> URL: https://issues.apache.org/jira/browse/MINIFI-504
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Build
>Affects Versions: 0.6.0
>Reporter: Nenad V. Nikolić
>Priority: Blocker
> Fix For: 1.14.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> After submitting the [PR #158|https://github.com/apache/nifi-minifi/pull/158]
> for a broken test (and underlying class) I realized the build breaks for an
> unrelated reason. The reason was {{commons-daemon}} version 1.1.0 being used
> which is not available on the
> [mirror|https://apache.claz.org/commons/daemon/binaries/windows/] anymore.
> Currently, there's only one, newer version 1.2.0 hosted on the mirror that
> should be used instead.
> Because of this issue with the build system it's not possible to submit any
> correct PRs at the moment, so I've set the priority to Blocker.
> This Jira issue is FYI as another PR to upgrade {{commons-deamon}} to 1.2.0
> is coming right up.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MINIFI-484) Fix new lines formatting of system admin guide
[ https://issues.apache.org/jira/browse/MINIFI-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-484: Fix Version/s: (was: 0.6.0) 1.14.0 > Fix new lines formatting of system admin guide > -- > > Key: MINIFI-484 > URL: https://issues.apache.org/jira/browse/MINIFI-484 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Documentation >Affects Versions: 0.6.0 >Reporter: Jeffrey T. Zemerick >Assignee: Jeffrey T. Zemerick >Priority: Trivial > Fix For: 1.14.0 > > > Fix new lines formatting of system admin guide. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-501) Allow specification of an SSL Context/properties outside of the config.yml
[ https://issues.apache.org/jira/browse/MINIFI-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-501: Fix Version/s: (was: 0.6.0) 1.14.0 > Allow specification of an SSL Context/properties outside of the config.yml > -- > > Key: MINIFI-501 > URL: https://issues.apache.org/jira/browse/MINIFI-501 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Agent Configuration/Installation >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > > With the typical exchange of flows as through the config change notifiers, it > can be unreasonable to expect that all properties would also be made > available to allow for securing things like site to site which are > defined/handled in nifi.properties in NiFi. We should allow the provisioning > of a context through bootstrap.conf to allow the config.yml to focus more on > the processing aspects. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-499) Evaluate dependency sources
[ https://issues.apache.org/jira/browse/MINIFI-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-499: Fix Version/s: (was: 0.6.0) 1.14.0 > Evaluate dependency sources > --- > > Key: MINIFI-499 > URL: https://issues.apache.org/jira/browse/MINIFI-499 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > Time Spent: 1h > Remaining Estimate: 0h > > As in NIFI-6323, performing a review of all dependency sources and upgrading > references to HTTPS where possible/applicable. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-508) Make Windows daemon inclusion a profile
[ https://issues.apache.org/jira/browse/MINIFI-508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-508: Fix Version/s: (was: 0.6.0) 1.14.0 > Make Windows daemon inclusion a profile > --- > > Key: MINIFI-508 > URL: https://issues.apache.org/jira/browse/MINIFI-508 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Build >Affects Versions: 0.5.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > As the Windows service executable relies on an outside source it could be > beneficial to have this process driven by a profile to mitigate those areas > where users do not care about having that support. The intent would be for > this to still remain in released convenience binaries as part of the RM > process but make it disabled by default -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-509) SSL Context defined in bootstrap Not Working?
[
https://issues.apache.org/jira/browse/MINIFI-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated MINIFI-509:
Fix Version/s: (was: 0.6.0)
1.14.0
> SSL Context defined in bootstrap Not Working?
> -
>
> Key: MINIFI-509
> URL: https://issues.apache.org/jira/browse/MINIFI-509
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
>Reporter: Ryan Whittington
>Assignee: Ferenc Kis
>Priority: Major
> Fix For: 1.14.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> I'm trying to set my SSL-Context-Service properties using the bootstrap.conf,
> but it doesn't seem to propagate through to the flow.xml.gz when minifi
> starts/reloads - and isn't available to use in my flow?
> As this feature was recently added in MINIFI-501 by [~aldrin], I'm building
> minifi from the master branch on github.
> bootstrap.conf:
>
> {code:java}
> # Security Properties #
> # These properties take precedence over any equivalent properties specified
> in config.yml #
> nifi.minifi.security.keystore=/my/test/keystore.jks
> nifi.minifi.security.keystoreType=JKS
> nifi.minifi.security.keystorePasswd=mykeystorepassword
> nifi.minifi.security.keyPasswd=mykeypassword
> nifi.minifi.security.truststore=/my/test/truststore.jks
> nifi.minifi.security.truststoreType=JKS
> nifi.minifi.security.truststorePasswd=mytruststorepassword
> nifi.minifi.security.ssl.protocol=TLS
> {code}
>
> flow.xml.gz once running:
> {noformat}
>
>
> 1
> 1
>
>
> Root-Group
> MiNiFi Flow
>
>
>
>
>
> {noformat}
> Am I doing something wrong, or is this not fully implemented yet?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MINIFI-512) Only allow bootstrap port to be set during initial startup
[ https://issues.apache.org/jira/browse/MINIFI-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-512: Fix Version/s: (was: 0.6.0) 1.14.0 > Only allow bootstrap port to be set during initial startup > -- > > Key: MINIFI-512 > URL: https://issues.apache.org/jira/browse/MINIFI-512 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Kevin Doran >Assignee: Kevin Doran >Priority: Minor > Fix For: 1.14.0 > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-477) Upgrade dependencies to NiFi 1.8.0
[ https://issues.apache.org/jira/browse/MINIFI-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-477: Fix Version/s: (was: 0.6.0) 1.14.0 > Upgrade dependencies to NiFi 1.8.0 > -- > > Key: MINIFI-477 > URL: https://issues.apache.org/jira/browse/MINIFI-477 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > > We should upgrade the shared libraries to those of NiFi 1.8.0 when released. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-493) NPE when converting old templates using toolkit
[ https://issues.apache.org/jira/browse/MINIFI-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-493: Fix Version/s: (was: 0.6.0) 1.14.0 > NPE when converting old templates using toolkit > --- > > Key: MINIFI-493 > URL: https://issues.apache.org/jira/browse/MINIFI-493 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Our handling of the changes to RPG ids uses a switch on a given encoding > version. Older versions of NiFi (verified with 0.4.0) do not provide this. > Accordingly, there is no reason why we cannot also convert older templates. > Some simple null guarding will allow us to treat older versions as the base > case where RPG IDs are treated the same as those encodings < 1.2 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-424) Expose bootstrap properties in the ConfigTransformer
[
https://issues.apache.org/jira/browse/MINIFI-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated MINIFI-424:
Fix Version/s: (was: 0.6.0)
1.14.0
> Expose bootstrap properties in the ConfigTransformer
>
>
> Key: MINIFI-424
> URL: https://issues.apache.org/jira/browse/MINIFI-424
> Project: Apache NiFi MiNiFi
> Issue Type: New Feature
>Reporter: Joe Percivall
>Assignee: Joe Percivall
>Priority: Major
> Fix For: 1.14.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The ConfigTransformer takes in the config.yml and creates the nifi.properties
> and flow.xml. In order to better support customizations on a per MiNiFi
> instance for things that aren't able to reference EL, we could expose the
> properties listed in the bootstrap.conf.
> As an example, the bootstrap conf could have properties identifying the S2S
> URL and port UUID to use. Then when MiNiFi pulls down the new config.yml it
> would translate the keys to their proper values as identified in the
> bootstrap.conf.
> The main unknown is what the "escape" identifiers would be. In EL it is "${
> . }" (not sure why Jira is formatting this with new lines). This would
> need to be specific enough that it doesn't collide with anything that'd be in
> the config.yml.
> Much further down the line, this could eventually evolve to expose ENV
> variables, key/values stored in a file, and maybe even basic functions as
> needed. Essentially a basic version of EL but I hesitate to call it that b/c
> I don't want users to expect all of that functionality. This should really be
> for things that can't be done via EL.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MINIFI-490) Generically support reporting tasks
[ https://issues.apache.org/jira/browse/MINIFI-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-490: Fix Version/s: (was: 0.6.0) 1.14.0 > Generically support reporting tasks > --- > > Key: MINIFI-490 > URL: https://issues.apache.org/jira/browse/MINIFI-490 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Nghia Le >Priority: Major > Fix For: 1.14.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-516) Override processor SSLs with parent SSL
[ https://issues.apache.org/jira/browse/MINIFI-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-516: Fix Version/s: (was: 0.6.0) 1.14.0 > Override processor SSLs with parent SSL > --- > > Key: MINIFI-516 > URL: https://issues.apache.org/jira/browse/MINIFI-516 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: GCHQ NiFi >Assignee: r65535 >Priority: Minor > Fix For: 1.14.0 > > Time Spent: 1h 40m > Remaining Estimate: 0h > > When using a ingestor to deploy flows to MiNiFi, processors using SSL > contexts don't start up as the sensitive properties are not passed along in > the NiFi templates. > A user should be able to set a boolean in the bootstrap.conf to tell MiNiFi > to ignore any custom SSL contexts in the config.yml, and repoint to the > parent SSL called "SSL-Context-Service" instead. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-497) С2 Server: wrong regex pattern in "getConfiguration" (NiFiRestConfigurationProvider.java)
[
https://issues.apache.org/jira/browse/MINIFI-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated MINIFI-497:
Fix Version/s: (was: 0.6.0)
1.14.0
> С2 Server: wrong regex pattern in "getConfiguration"
> (NiFiRestConfigurationProvider.java)
> -
>
> Key: MINIFI-497
> URL: https://issues.apache.org/jira/browse/MINIFI-497
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Command and Control
>Affects Versions: 0.5.0
>Reporter: Vladimir Mikhailov
>Assignee: Vladimir Mikhailov
>Priority: Critical
> Labels: easyfix
> Fix For: 1.14.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> C2 Server can't get from NiFi templates with versions v10+, only v1-v9.
> The reason is an error in the "getConfiguration" function, where
> "filenamePattern" is determined.
> Wrong code (maybe a typo?):
> {code:java}
> String filenamePattern =
> Arrays.stream(filename.split(Pattern.quote("${version}"),
> -1)).map(Pattern::quote).collect(Collectors.joining("([0-9+])"));
> {code}
> It should be:
> {code:java}
> String filenamePattern =
> Arrays.stream(filename.split(Pattern.quote("${version}"),
> -1)).map(Pattern::quote).collect(Collectors.joining("([0-9]+)"));
> {code}
> {code:java}
> [0-9+] -> [0-9]+{code}
> Link to source code:
> https://github.com/apache/nifi-minifi/blob/master/minifi-c2/minifi-c2-provider/minifi-c2-provider-nifi-rest/src/main/java/org/apache/nifi/minifi/c2/provider/nifi/rest/NiFiRestConfigurationProvider.java#L105
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MINIFI-495) minifi-docker module should depend on minifi-assembly
[ https://issues.apache.org/jira/browse/MINIFI-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-495: Fix Version/s: (was: 0.6.0) 1.14.0 > minifi-docker module should depend on minifi-assembly > - > > Key: MINIFI-495 > URL: https://issues.apache.org/jira/browse/MINIFI-495 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Docker >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Currently the docker module does not depend on the assembly. This means that > for multhreaded builds there is a potential that the docker build will make > use of what is a stale assembly. Or, for a clean state, will not be able to > build when activated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-461) Display application startup time in human-readable seconds
[
https://issues.apache.org/jira/browse/MINIFI-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated MINIFI-461:
Fix Version/s: (was: 0.6.0)
1.14.0
> Display application startup time in human-readable seconds
> --
>
> Key: MINIFI-461
> URL: https://issues.apache.org/jira/browse/MINIFI-461
> Project: Apache NiFi MiNiFi
> Issue Type: Improvement
> Components: Core Framework
>Affects Versions: 0.5.0
>Reporter: Andy LoPresto
>Assignee: Aldrin Piri
>Priority: Minor
> Labels: log, startup-time
> Fix For: 1.14.0
>
>
> The application log should display the startup time similar to the way the
> Apache NiFi boot process now displays the startup time in both nanoseconds
> and human-readable seconds.
> {code}
> 2018-06-29 15:23:43,041 INFO [main] org.apache.nifi.minifi.MiNiFi Controller
> initialization took 546376888 nanoseconds.
> {code}
> Should become:
> {code}
> 2018-06-29 15:23:43,041 INFO [main] org.apache.nifi.minifi.MiNiFi Controller
> initialization took 546376888 nanoseconds (0.5 seconds).
> {code}
> This is easier for humans to understand when quickly looking at the logs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MINIFI-245) Expose repository implementation configuration
[ https://issues.apache.org/jira/browse/MINIFI-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-245: Fix Version/s: (was: 0.6.0) (was: 1.0.0) 1.14.0 > Expose repository implementation configuration > -- > > Key: MINIFI-245 > URL: https://issues.apache.org/jira/browse/MINIFI-245 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Agent Configuration/Installation >Reporter: Aldrin Piri >Assignee: Matt Burgess >Priority: Minor > Fix For: 1.14.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Currently there is no way to specify the backing provenance or content > repository implementation in configuration. This should likely be provided > in the bootstrap to allow users to leverage volatile or other, future, > implementations. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-483) Add Ubuntu 16/18 to supported list
[ https://issues.apache.org/jira/browse/MINIFI-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-483: Fix Version/s: (was: 0.6.0) 1.14.0 > Add Ubuntu 16/18 to supported list > -- > > Key: MINIFI-483 > URL: https://issues.apache.org/jira/browse/MINIFI-483 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Documentation >Reporter: Jeffrey T. Zemerick >Assignee: Jeffrey T. Zemerick >Priority: Trivial > Fix For: 1.14.0 > > > Add Ubuntu 16/18 to supported list. I've used MiNiFi extensively on both > without issues. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-473) Make formatting in Sys Admin Guide and Java Quick Start Guide consistent with NiFi documentation
[ https://issues.apache.org/jira/browse/MINIFI-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-473: Fix Version/s: (was: 0.6.0) 1.14.0 > Make formatting in Sys Admin Guide and Java Quick Start Guide consistent with > NiFi documentation > > > Key: MINIFI-473 > URL: https://issues.apache.org/jira/browse/MINIFI-473 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Documentation >Affects Versions: 0.5.0 >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Minor > Fix For: 1.14.0 > > > Check/update formatting throughout these docs to make consistent with NiFi > and NiFi Registry documentation when referencing files and directories. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-478) OrderedPropertiesTest fails on Java 11 / OS X
[ https://issues.apache.org/jira/browse/MINIFI-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-478: Fix Version/s: (was: 0.6.0) 1.14.0 > OrderedPropertiesTest fails on Java 11 / OS X > - > > Key: MINIFI-478 > URL: https://issues.apache.org/jira/browse/MINIFI-478 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Dustin Rodrigues >Assignee: Nenad V. Nikolić >Priority: Major > Fix For: 1.14.0 > > Time Spent: 1h 20m > Remaining Estimate: 0h > > When running on OS X 10.14 ( Mojave ) with openjdk 11, the > OrderedPropertiesTest is failing. When using jdk1.8.0_192 instead, the test > succeeds. > > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.05 sec <<< > FAILURE! - in org.apache.nifi.minifi.bootstrap.util.OrderedPropertiesTest > testOrderedProperties(org.apache.nifi.minifi.bootstrap.util.OrderedPropertiesTest) > Time elapsed: 0.05 sec <<< FAILURE! > org.junit.ComparisonFailure: expected:<[prop1=newVal1]> but was:<[#this is > property 2]> > at org.junit.Assert.assertEquals(Assert.java:115) > at org.junit.Assert.assertEquals(Assert.java:144) > at > org.apache.nifi.minifi.bootstrap.util.OrderedPropertiesTest.testOrderedProperties(OrderedPropertiesTest.java:49) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-536) Allow for more ConfigTransformer overrides in bootstrap.conf properties
[ https://issues.apache.org/jira/browse/MINIFI-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-536: Fix Version/s: (was: 0.6.0) 1.14.0 > Allow for more ConfigTransformer overrides in bootstrap.conf properties > --- > > Key: MINIFI-536 > URL: https://issues.apache.org/jira/browse/MINIFI-536 > Project: Apache NiFi MiNiFi > Issue Type: New Feature >Reporter: Kevin Doran >Priority: Major > Fix For: 1.14.0 > > > MiNiFi change ingestors generate a flow.xml.gz and niti.properties file from > a config.yml. > However, there are some properties that users want to set on the agent to > prevent them being overwritten by config.yml updates via a change ingestor. > Some of this was already done for security properties. See > [https://github.com/apache/nifi-minifi/pull/167] > This ticket is just to allow more overrides to be set using this method in > bootstrap.conf. For example, Repository settings. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-523) 0.6.0 Release Notes
[ https://issues.apache.org/jira/browse/MINIFI-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-523: Fix Version/s: (was: 0.6.0) 1.14.0 > 0.6.0 Release Notes > --- > > Key: MINIFI-523 > URL: https://issues.apache.org/jira/browse/MINIFI-523 > Project: Apache NiFi MiNiFi > Issue Type: Task >Affects Versions: 0.6.0 >Reporter: Nathan Gough >Priority: Major > Labels: release, releasenotes > Fix For: 1.14.0 > > > This issue is tracking what work needs to be done for release notes to > release 0.6.0. > * Include dependency version changes > * Notify users that the OkHTTP upgrade will now require certificates to > include a DNS SAN entry, as recommended by > [https://tools.ietf.org/html/rfc6125]. Users will find that certificates > without a valid SAN entry in certificates used with MiNiFi will result in > failed TLS negotiation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-162) Capture enhanced build information
[ https://issues.apache.org/jira/browse/MINIFI-162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-162: Fix Version/s: (was: 0.6.0) 1.14.0 > Capture enhanced build information > -- > > Key: MINIFI-162 > URL: https://issues.apache.org/jira/browse/MINIFI-162 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Minor > Fix For: 1.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Work was done for NiFi (NIFI-2215) to expose additional information in the > About box. While we do not have a graphical view, capturing this information > in the minifi.properties file would be helpful for debugging and general > awareness of the system. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-537) Possible NullPointerException in BootstrapTransformer
[
https://issues.apache.org/jira/browse/MINIFI-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated MINIFI-537:
Fix Version/s: (was: 0.6.0)
1.14.0
> Possible NullPointerException in BootstrapTransformer
> -
>
> Key: MINIFI-537
> URL: https://issues.apache.org/jira/browse/MINIFI-537
> Project: Apache NiFi MiNiFi
> Issue Type: New Feature
>Reporter: Kevin Doran
>Assignee: Kevin Doran
>Priority: Major
> Fix For: 1.14.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> [https://github.com/apache/nifi-minifi/pull/167] introduced the ability to
> override security properties and sensitive properties in bootstrap.conf
> When using this feature, there is a potential NPE that prevents MiNiFi from
> starting.
> Steps to reproduce:
> In bootstrap.conf set any of the SSL/TLS properties, for example:
>
> {noformat}
> nifi.minifi.security.keystoreType=jks{noformat}
> Leave this unset / blank:
>
>
> {noformat}
> nifi.minifi.sensitive.props.key={noformat}
>
>
> Start minifi and observe the following in app.log:
> {noformat}
> 2020-08-27 10:12:10,877 INFO [main] o.a.n.m.bootstrap.util.ConfigTransformer
> Bootstrap flow override: Replaced security properties2020-08-27 10:12:10,877
> INFO [main] o.a.n.m.bootstrap.util.ConfigTransformer Bootstrap flow override:
> Replaced security properties2020-08-27 10:12:10,881 ERROR [main]
> o.apache.nifi.minifi.bootstrap.RunMiNiFi The config file is malformed, unable
> to
> start.org.apache.nifi.minifi.bootstrap.configuration.ConfigurationChangeException:
> Failed to parse the config YAML while creating the nifi.properties at
> org.apache.nifi.minifi.bootstrap.util.ConfigTransformer.writeNiFiProperties(ConfigTransformer.java:290)
> at
> org.apache.nifi.minifi.bootstrap.util.ConfigTransformer.transformConfigFile(ConfigTransformer.java:120)
> at
> org.apache.nifi.minifi.bootstrap.RunMiNiFi.performTransformation(RunMiNiFi.java:1712)
> at org.apache.nifi.minifi.bootstrap.RunMiNiFi.start(RunMiNiFi.java:1180) at
> org.apache.nifi.minifi.bootstrap.RunMiNiFi.main(RunMiNiFi.java:244)Caused by:
> java.lang.NullPointerException: null at
> java.util.Hashtable.put(Hashtable.java:460) at
> org.apache.nifi.minifi.bootstrap.util.OrderedProperties.put(OrderedProperties.java:45)
> at java.util.Properties.setProperty(Properties.java:166) at
> org.apache.nifi.minifi.bootstrap.util.OrderedProperties.setProperty(OrderedProperties.java:62)
> at
> org.apache.nifi.minifi.bootstrap.util.ConfigTransformer.writeNiFiProperties(ConfigTransformer.java:260)
> ... 4 common frames omitted{noformat}
> This is because when SecurityPropertiesSchema is created (caused by the
> override properties in bootstrap.conf), the nested SensitivePropsSchema is
> created, but initialized with a null key. This causes the NPE when this
> property is accessed later (unchecked) in
> ConfigTransformer.writeNiFiProperties.
> I think the best solution here is to always initialize
> SensitivePropsSchema.key to its default value (empty string) which is what
> happens when it is created normally without the bootstrap.conf overrides.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MINIFI-505) Change digest algorithm to SHA-512
[ https://issues.apache.org/jira/browse/MINIFI-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-505: Fix Version/s: (was: 0.6.0) 1.14.0 > Change digest algorithm to SHA-512 > -- > > Key: MINIFI-505 > URL: https://issues.apache.org/jira/browse/MINIFI-505 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Nenad V. Nikolić >Assignee: Nenad V. Nikolić >Priority: Major > Fix For: 1.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > > In the light of a digest algorithm change in the [PR > #157|https://github.com/apache/nifi-minifi/pull/157/commits/c13e286fdf380f315a7951573edd7d475b74372f#diff-081c5543514deb23ccd8543465113b8dR70] > from [~aldrin] and our agreement in PR #161 to keep that change separate > from the rest, the digest algorithm should be changed separately. > PR is coming shortly after PR #161 is approved and merged to master. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-496) Multiple RPGs to the same NiFi instance will preclude successful transformation
[ https://issues.apache.org/jira/browse/MINIFI-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-496: Fix Version/s: (was: 0.6.0) 1.14.0 > Multiple RPGs to the same NiFi instance will preclude successful > transformation > --- > > Key: MINIFI-496 > URL: https://issues.apache.org/jira/browse/MINIFI-496 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Processing Configuration >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > > If a template references the same NiFi instance within more than one RPGs, > the transformer will be nonplussed over the reuse of a unique id. While we > need certain unique constraints for components, this is a special case that > needs separate handling. Will supply a template that exhibits this issue. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-540) Write nifi.kerberos.krb5.file to nifi.properties
[ https://issues.apache.org/jira/browse/MINIFI-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-540: Fix Version/s: (was: 0.6.0) 1.14.0 > Write nifi.kerberos.krb5.file to nifi.properties > > > Key: MINIFI-540 > URL: https://issues.apache.org/jira/browse/MINIFI-540 > Project: Apache NiFi MiNiFi > Issue Type: New Feature > Components: Processing Configuration >Affects Versions: 0.5.0 >Reporter: Javi Roman >Assignee: Javi Roman >Priority: Minor > Fix For: 1.14.0 > > > Add System Properties -> Kerberos Properties for adding (at least) the > krb5.conf file for using in processors such as GetHDFSEvents. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-472) Update dependencies as reported by dependencies versions plugin
[ https://issues.apache.org/jira/browse/MINIFI-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-472: Fix Version/s: (was: 0.6.0) 1.14.0 > Update dependencies as reported by dependencies versions plugin > --- > > Key: MINIFI-472 > URL: https://issues.apache.org/jira/browse/MINIFI-472 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > > NIFI-4806 provided an update across used libraries to address outstanding > CVEs. We should perform a similar scan, analysis and update where > appropriate. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-468) Update Docker resources to reflect current versioning
[ https://issues.apache.org/jira/browse/MINIFI-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-468: Fix Version/s: (was: 0.6.0) 1.14.0 > Update Docker resources to reflect current versioning > - > > Key: MINIFI-468 > URL: https://issues.apache.org/jira/browse/MINIFI-468 > Project: Apache NiFi MiNiFi > Issue Type: New Feature >Affects Versions: 0.5.0 >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > > A few of the Docker resources were not up to date with the current release > and need some adjustments. Additionally, it appears there are some malformed > URLs in the Dockerfile. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-530) Upgrade jackson-databind dependency version
[ https://issues.apache.org/jira/browse/MINIFI-530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-530: Fix Version/s: (was: 1.0.0) 1.14.0 > Upgrade jackson-databind dependency version > --- > > Key: MINIFI-530 > URL: https://issues.apache.org/jira/browse/MINIFI-530 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 0.5.0 >Reporter: M Tien >Assignee: M Tien >Priority: Major > Labels: dependencies > Fix For: 1.14.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Upgrade jackson-databind dependency. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-507) Audit MiNiFi dependencies for upgrade
[ https://issues.apache.org/jira/browse/MINIFI-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-507: Fix Version/s: (was: 0.6.0) 1.14.0 > Audit MiNiFi dependencies for upgrade > - > > Key: MINIFI-507 > URL: https://issues.apache.org/jira/browse/MINIFI-507 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Nathan Gough >Assignee: Nathan Gough >Priority: Major > Fix For: 1.14.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Check the MiNiFi project for dependencies that need to be upgraded. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-511) Allow Provenance Reporting to be configured outside of the config.yml
[ https://issues.apache.org/jira/browse/MINIFI-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-511: Fix Version/s: (was: 0.6.0) 1.14.0 > Allow Provenance Reporting to be configured outside of the config.yml > - > > Key: MINIFI-511 > URL: https://issues.apache.org/jira/browse/MINIFI-511 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Agent Configuration/Installation >Reporter: GCHQ NiFi >Assignee: GCHQ NiFi >Priority: Major > Fix For: 1.14.0 > > Time Spent: 1h > Remaining Estimate: 0h > > When using the MiNiFi config change notifiers, it's not currently possible to > set the provenance reporting properties. > MINIFI-501 allowed for the SSL context properties to be set in the bootstrap, > so it makes sense for the provenance reporting to be set in the same way. > I've created a fork with the changes completed already, so will link this > ticket to a pull request. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-510) Migrate Travis away from OracleJDK8 which seems to be problematic
[ https://issues.apache.org/jira/browse/MINIFI-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-510: Fix Version/s: (was: 0.6.0) 1.14.0 > Migrate Travis away from OracleJDK8 which seems to be problematic > - > > Key: MINIFI-510 > URL: https://issues.apache.org/jira/browse/MINIFI-510 > Project: Apache NiFi MiNiFi > Issue Type: Task >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > > It seems configuration of Travis has changed such that Oracle JDK 8 is no > longer available. We should migrate to supported versions of 8. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-532) Support more configurable properties for content and provenance repositories
[ https://issues.apache.org/jira/browse/MINIFI-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-532: Fix Version/s: (was: 0.6.0) (was: 1.0.0) 1.14.0 > Support more configurable properties for content and provenance repositories > > > Key: MINIFI-532 > URL: https://issues.apache.org/jira/browse/MINIFI-532 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.14.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Very few properties are configurable for the content and provenance > repositories, regardless of the specified implementation. At the very least > the following NiFi properties should be made available for configuration via > config.yml: > Content Repo: > nifi.content.repository.archive.max.retention.period > nifi.content.repository.archive.max.usage.percentage > nifi.content.repository.archive.enabled > MiNiFi Persistent Provenance Repo: > nifi.provenance.repository.index.shard.size > nifi.provenance.repository.max.storage.size > nifi.provenance.repository.max.storage.time > Volatile Provenance Repo: > nifi.provenance.repository.buffer.size -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-481) Update to use new handling of ExtensionManager
[ https://issues.apache.org/jira/browse/MINIFI-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-481: Fix Version/s: (was: 0.6.0) 1.14.0 > Update to use new handling of ExtensionManager > -- > > Key: MINIFI-481 > URL: https://issues.apache.org/jira/browse/MINIFI-481 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Core Framework >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > > ExtensionManager was refactored to aid in extension registry efforts and has > migrated away from the static instance previously used. The two commits of > most interest are > https://github.com/apache/nifi/commit/fdd8cdbb31a8977967d4437ba9a09104bf6cf450 > and > https://github.com/apache/nifi/commit/931bb0bc3b1c0205b260261ce9730af87204e115 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-469) support osx in travis build
[ https://issues.apache.org/jira/browse/MINIFI-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-469: Fix Version/s: (was: 0.6.0) 1.14.0 > support osx in travis build > --- > > Key: MINIFI-469 > URL: https://issues.apache.org/jira/browse/MINIFI-469 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Dustin Rodrigues >Assignee: Dustin Rodrigues >Priority: Major > Fix For: 1.14.0 > > > Update .travis.yml to support automated OSX builds. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-470) Update NiFi dependency to 1.7.1
[ https://issues.apache.org/jira/browse/MINIFI-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-470: Fix Version/s: (was: 0.6.0) 1.14.0 > Update NiFi dependency to 1.7.1 > --- > > Key: MINIFI-470 > URL: https://issues.apache.org/jira/browse/MINIFI-470 > Project: Apache NiFi MiNiFi > Issue Type: New Feature >Affects Versions: 0.6.0 >Reporter: Jeffrey T. Zemerick >Assignee: Jeffrey T. Zemerick >Priority: Major > Fix For: 1.14.0 > > > Update NiFi dependency to 1.7.1. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-513) CLONE - Updated bootstrap port handling causes restarts to fail
[
https://issues.apache.org/jira/browse/MINIFI-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated MINIFI-513:
Fix Version/s: (was: 0.6.0)
1.14.0
> CLONE - Updated bootstrap port handling causes restarts to fail
> ---
>
> Key: MINIFI-513
> URL: https://issues.apache.org/jira/browse/MINIFI-513
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
>Reporter: Aldrin Piri
>Assignee: Bryan Bende
>Priority: Blocker
> Fix For: 1.14.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> NIFI-6653 introduced a way to avoid the port being changed to prevent a
> possible hijacking of that port to provide other commands than those
> explicitly between bootstrap and the nifi process. This causes issues when
> the NiFi process dies and precludes restart (the default functionality
> enabled out of the box).
> To recreate, build/run NiFi off of current master and kill the NiFi process.
> This will result in the following (when an additional nifi.sh status is
> carried out).
> {quote}2019-09-25 17:10:55,601 WARN [main] org.apache.nifi.bootstrap.RunNiFi
> Apache NiFi appears to have died. Restarting...
> 2019-09-25 17:10:55,620 INFO [main] org.apache.nifi.bootstrap.Command
> Launched Apache NiFi with Process ID 2088
> 2019-09-25 17:10:55,621 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Successfully started Apache NiFi with PID 2088
> 2019-09-25 17:10:56,174 WARN [NiFi Bootstrap Command Listener]
> org.apache.nifi.bootstrap.RunNiFi Blocking attempt to change NiFi command
> port and secret after they have already been initialized. requestedPort=37871
> 2019-09-25 17:11:50,783 INFO [main] o.a.n.b.NotificationServiceManager
> Successfully loaded the following 0 services: []
> 2019-09-25 17:11:50,785 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STARTED
> 2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_STOPPED
> 2019-09-25 17:11:50,786 INFO [main] org.apache.nifi.bootstrap.RunNiFi
> Registered no Notification Services for Notification Type NIFI_DIED
> 2019-09-25 17:11:50,809 INFO [main] org.apache.nifi.bootstrap.Command Apache
> NiFi is running at PID 2088 but is not responding to ping requests{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MINIFI-526) Add anchors to MiNiFi admin guide
[ https://issues.apache.org/jira/browse/MINIFI-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-526: Fix Version/s: (was: 0.6.0) 1.14.0 > Add anchors to MiNiFi admin guide > - > > Key: MINIFI-526 > URL: https://issues.apache.org/jira/browse/MINIFI-526 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Documentation >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Minor > Fix For: 1.14.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Add HTML anchors to admin guide so different sections are easy to reference > and link to as needed. > [https://nifi.apache.org/minifi/system-admin-guide.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-522) Fixed Access denied to: http://jcenter.bintray.com which caused Failed to execute goal on project minifi-standard-nar
[
https://issues.apache.org/jira/browse/MINIFI-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated MINIFI-522:
Fix Version/s: (was: 0.6.0)
1.14.0
> Fixed Access denied to: http://jcenter.bintray.com which caused Failed to
> execute goal on project minifi-standard-nar
> -
>
> Key: MINIFI-522
> URL: https://issues.apache.org/jira/browse/MINIFI-522
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
>Reporter: sapinkumar amin
>Assignee: sapinkumar amin
>Priority: Blocker
> Fix For: 1.14.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {code:java}
> mvn clean install {code}
> throws below error
> {code:java}
> [INFO] minifi-update-attribute-nar SUCCESS [ 0.326
> s]
> [INFO] minifi-standard-nar FAILURE [ 1.198
> s]
> [INFO] minifi-ssl-context-service-nar . SKIPPED
> [INFO] minifi-docs SKIPPED
> [INFO] minifi-assembly SKIPPED
> [INFO] minifi-toolkit . SKIPPED
> [INFO] minifi-toolkit-configuration ... SKIPPED
> [INFO] minifi-toolkit-assembly SKIPPED
> [INFO] minifi-docker .. SKIPPED
> [INFO] minifi-c2 .. SKIPPED
> [INFO] minifi-c2-api .. SKIPPED
> [INFO] minifi-c2-cache SKIPPED
> [INFO] minifi-c2-cache-filesystem . SKIPPED
> [INFO] minifi-c2-cache-s3 . SKIPPED
> [INFO] minifi-c2-provider . SKIPPED
> [INFO] minifi-c2-provider-util SKIPPED
> [INFO] minifi-c2-provider-cache ... SKIPPED
> [INFO] minifi-c2-provider-delegating .. SKIPPED
> [INFO] minifi-c2-provider-nifi-rest ... SKIPPED
> [INFO] minifi-c2-service .. SKIPPED
> [INFO] minifi-c2-jetty SKIPPED
> [INFO] minifi-c2-assembly . SKIPPED
> [INFO] minifi-c2-docker ... SKIPPED
> [INFO] minifi-c2-integration-tests SKIPPED
> [INFO] minifi-integration-tests ... SKIPPED
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 29.209 s
> [INFO] Finished at: 2020-01-14T14:02:00-08:00
> [INFO]
>
> [ERROR] Failed to execute goal on project minifi-standard-nar: Could not
> resolve dependencies for project
> org.apache.nifi.minifi:minifi-standard-nar:nar:0.6.0-SNAPSHOT: Failed to
> collect dependencies at org.apache.nifi:nifi-standard-processors:jar:1.8.0 ->
> org.apache.nifi:nifi-syslog-utils:jar:1.8.0 ->
> com.github.palindromicity:simple-syslog-5424:jar:0.0.8: Failed to read
> artifact descriptor for
> com.github.palindromicity:simple-syslog-5424:jar:0.0.8: Could not transfer
> artifact com.github.palindromicity:simple-syslog-5424:pom:0.0.8 from/to
> jcenter (http://jcenter.bintray.com): Access denied to:
> http://jcenter.bintray.com/com/github/palindromicity/simple-syslog-5424/0.0.8/simple-syslog-5424-0.0.8.pom
> -> [Help 1]
> {code}
>
> From Jan13th : 2020 , access to jcenter.bintray.com is only allowed over
> https protocol (previously it use to support http and https).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MINIFI-503) Update commons-daemon to 1.2
[ https://issues.apache.org/jira/browse/MINIFI-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-503: Fix Version/s: (was: 0.6.0) 1.14.0 > Update commons-daemon to 1.2 > > > Key: MINIFI-503 > URL: https://issues.apache.org/jira/browse/MINIFI-503 > Project: Apache NiFi MiNiFi > Issue Type: Task > Components: Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > Time Spent: 40m > Remaining Estimate: 0h > > Commons daemon recently released 1.2 which is causing builds to break as 1.1 > is no longer available. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-528) Add Documentation for Minifi Arm64 Docker Image
[ https://issues.apache.org/jira/browse/MINIFI-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-528: Fix Version/s: (was: 0.6.0) 1.14.0 > Add Documentation for Minifi Arm64 Docker Image > --- > > Key: MINIFI-528 > URL: https://issues.apache.org/jira/browse/MINIFI-528 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: kaustav mukherjee >Assignee: kaustav mukherjee >Priority: Major > Fix For: 1.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-524) Adding ARM 64 V8 Docker for Minifi Java for Execution on Raspberry Pi
[ https://issues.apache.org/jira/browse/MINIFI-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-524: Fix Version/s: (was: 0.6.0) 1.14.0 > Adding ARM 64 V8 Docker for Minifi Java for Execution on Raspberry Pi > - > > Key: MINIFI-524 > URL: https://issues.apache.org/jira/browse/MINIFI-524 > Project: Apache NiFi MiNiFi > Issue Type: New Feature > Components: Docker >Affects Versions: 0.6.0 > Environment: UBUNTU 19.10 ARM64_V8 for Raspberry Pi 4 >Reporter: kaustav mukherjee >Assignee: kaustav mukherjee >Priority: Major > Labels: ARM, Docker > Fix For: 1.14.0 > > Attachments: dockerhub_ARM_64_V8.tar.gz > > Time Spent: 2h > Remaining Estimate: 0h > > Adding ARM_V8 Docker Image for minifi java so that it can execute on Rapberry > Pi 4 abd any other edge Devices That needs to the Minifi Flow -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-471) Upgrade Jetty version
[ https://issues.apache.org/jira/browse/MINIFI-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-471: Fix Version/s: (was: 0.6.0) 1.14.0 > Upgrade Jetty version > - > > Key: MINIFI-471 > URL: https://issues.apache.org/jira/browse/MINIFI-471 > Project: Apache NiFi MiNiFi > Issue Type: Task >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > > We should update and verify functionality with a more up to date Jetty > libraries to ensure up to date fixes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-520) Migrate Docker image names to mirror those of the public repos
[ https://issues.apache.org/jira/browse/MINIFI-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-520: Fix Version/s: (was: 0.6.0) 1.14.0 > Migrate Docker image names to mirror those of the public repos > -- > > Key: MINIFI-520 > URL: https://issues.apache.org/jira/browse/MINIFI-520 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > Time Spent: 10m > Remaining Estimate: 0h > > For consistency, it would be helpful to have the docker images reflect the > image tags used in Docker Hub. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-521) minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id" confused by targetId?
[
https://issues.apache.org/jira/browse/MINIFI-521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated MINIFI-521:
Fix Version/s: (was: 0.6.0)
1.14.0
> minifi-toolkit-0.5.0: "Connection with id ... has invalid destination id"
> confused by targetId?
> ---
>
> Key: MINIFI-521
> URL: https://issues.apache.org/jira/browse/MINIFI-521
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Components: Agent Configuration/Installation
>Affects Versions: 0.5.0
> Environment: version: '3'
> services:
> nifi:
> image: apache/nifi:1:10.0
> minifi:
> image: apache/nifi-minifi:0.5.0
> minifi-toolkit-0.5.0, Windows
>Reporter: Sebastian Napiorkowski
>Assignee: Aldrin Piri
>Priority: Minor
> Fix For: 1.14.0
>
> Attachments: MiNiFi-buggy.xml, MiNiFi-expected.xml, config-buggy.yml,
> config-expected.yml, config.yml, minifi-flow.xml
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> I followed this tutorial: [Getting started with
> MiNiFi|https://nifi.apache.org/minifi/getting-started.html]
> And the problem was that, while transforming the Template to the yml-file, it
> failed with: "Connection with id 10de7342-41ef-37a5-- has
> invalid destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd"
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-buggy.xml
> config-buggy.yml
> There are validation errors with the template, still outputting YAML but it
> will need to be edited.
> Connection with id 10de7342-41ef-37a5-- has invalid
> destination id 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> By the help of brosander@github (Thank you, mate!) we discovered that the
> tool is confused by the targetId property:
> {code:xml}
>
>
>
>
>
> 1
> true
> true
>
> db4d2e20-016e-1000-d3c7-73a67e2b1d67
> 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> input_minifi
>
> dadd7f29-016e-1000-3c91-89495c813674
> false
> false
> false
>
>
> {code}
> just by removing the {{targetId}}, the toolkit runs through:
> {code:java}
> minifi-toolkit-0.5.0\bin\config.bat transform MiNiFi-expected.xml
> config-expected.yml
> No validation errors found in converted configuration.
> {code}
> The produced files differ:
> {code:java}
> diff config-buggy.yml config-expected.yml
> 101c101
> < - id: dadd7f29-016e-1000-3c91-89495c813674
> ---
> > - id: 9b02eb45-3c2d-3fb4-91cf-880d5038c0cd
> {code}
> -I tested it and NiFi discovers MiNiFi, everything seems fine.-
> EDIT:
> I celebrated to early. Removing the {{targetId}} is *not* a working
> workaround. The easiest way to get around this issue is to downgrade NiFi
> from 1.10 to 1.9.2.
> Originally I thought this is a MiNiFi issue, but now I'm thinking that
> something changed in NiFi from 1.9.2 to 1.10.0 when exporting Templates. The
> ids are mixed up. This could be a much more critical bug, than I initially
> thought.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MINIFI-519) Add recommendations for antivirus exclusions to Admin guide
[ https://issues.apache.org/jira/browse/MINIFI-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-519: Fix Version/s: (was: 0.6.0) 1.14.0 > Add recommendations for antivirus exclusions to Admin guide > --- > > Key: MINIFI-519 > URL: https://issues.apache.org/jira/browse/MINIFI-519 > Project: Apache NiFi MiNiFi > Issue Type: Improvement >Reporter: Andrew M. Lim >Assignee: Andrew M. Lim >Priority: Minor > Fix For: 1.14.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Add similar section regarding antivirus exclusions to MiNiFi Admin Guide that > was added to NiFi Admin Guide via NIFI-6553 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-506) Change minifi-assembly antrun "tasks" tags to "target"
[ https://issues.apache.org/jira/browse/MINIFI-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-506: Fix Version/s: (was: 0.6.0) 1.14.0 > Change minifi-assembly antrun "tasks" tags to "target" > -- > > Key: MINIFI-506 > URL: https://issues.apache.org/jira/browse/MINIFI-506 > Project: Apache NiFi MiNiFi > Issue Type: Improvement > Components: Build >Reporter: Aldrin Piri >Assignee: Aldrin Piri >Priority: Major > Fix For: 1.14.0 > > Time Spent: 20m > Remaining Estimate: 0h > > "tasks" is deprecated as per the plugin. > [WARNING] Parameter tasks is deprecated, use target instead -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MINIFI-518) Version issue with httpcomponents
[ https://issues.apache.org/jira/browse/MINIFI-518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated MINIFI-518: Fix Version/s: (was: 0.6.0) 1.14.0 > Version issue with httpcomponents > - > > Key: MINIFI-518 > URL: https://issues.apache.org/jira/browse/MINIFI-518 > Project: Apache NiFi MiNiFi > Issue Type: Bug > Components: Build >Affects Versions: 0.6.0 >Reporter: James >Assignee: James >Priority: Minor > Fix For: 1.14.0 > > Time Spent: 50m > Remaining Estimate: 0h > > The version of httpcomponents in the latest 0.6.0 pom causes and issue with > using a postHTTP with a security context defined (although I think its > generic to anything trying to use the SSLContextBuilder class). > The pom currently references; > > org.apache.httpcomponents > httpcore > 4.4.4 > > > But need to reference a later version, 4.4.12 works and is the latest. > I'll create a pull request so you can test the updated version. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (MINIFI-550) Failed to capture component stats for Stats History
[
https://issues.apache.org/jira/browse/MINIFI-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess resolved MINIFI-550.
-
Resolution: Fixed
> Failed to capture component stats for Stats History
> ---
>
> Key: MINIFI-550
> URL: https://issues.apache.org/jira/browse/MINIFI-550
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Environment: Windows (Server 2013 till 10)
>Reporter: Rene Weidlinger
>Priority: Major
> Fix For: 1.14.0
>
>
> Minifi throws this error every 60 seconds
>
> {code:java}
> 2021-04-07 10:53:05,523 ERROR [Timer-Driven Process Thread-2]
> o.apache.nifi.controller.FlowController Failed to capture component stats for
> Stats History
> java.lang.NullPointerException: null
> at
> org.apache.nifi.diagnostics.SystemDiagnostics.getOpenFileHandles(SystemDiagnostics.java:224)
> at
> org.apache.nifi.controller.FlowController.getNodeStatusSnapshot(FlowController.java:3056)
> at
> org.apache.nifi.controller.FlowController.access$400(FlowController.java:234)
> at
> org.apache.nifi.controller.FlowController$2.run(FlowController.java:708)
> at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown
> Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (MINIFI-550) Failed to capture component stats for Stats History
[
https://issues.apache.org/jira/browse/MINIFI-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess updated MINIFI-550:
Fix Version/s: 1.14.0
> Failed to capture component stats for Stats History
> ---
>
> Key: MINIFI-550
> URL: https://issues.apache.org/jira/browse/MINIFI-550
> Project: Apache NiFi MiNiFi
> Issue Type: Bug
> Environment: Windows (Server 2013 till 10)
>Reporter: Rene Weidlinger
>Priority: Major
> Fix For: 1.14.0
>
>
> Minifi throws this error every 60 seconds
>
> {code:java}
> 2021-04-07 10:53:05,523 ERROR [Timer-Driven Process Thread-2]
> o.apache.nifi.controller.FlowController Failed to capture component stats for
> Stats History
> java.lang.NullPointerException: null
> at
> org.apache.nifi.diagnostics.SystemDiagnostics.getOpenFileHandles(SystemDiagnostics.java:224)
> at
> org.apache.nifi.controller.FlowController.getNodeStatusSnapshot(FlowController.java:3056)
> at
> org.apache.nifi.controller.FlowController.access$400(FlowController.java:234)
> at
> org.apache.nifi.controller.FlowController$2.run(FlowController.java:708)
> at org.apache.nifi.engine.FlowEngine$2.run(FlowEngine.java:110)
> at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown
> Source)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> at java.lang.Thread.run(Unknown Source)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (MINIFI-547)
[ https://issues.apache.org/jira/browse/MINIFI-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess resolved MINIFI-547. - Resolution: Duplicate > name="Target" value="System.out"/> > > > Key: MINIFI-547 > URL: https://issues.apache.org/jira/browse/MINIFI-547 > Project: Apache NiFi MiNiFi > Issue Type: Bug >Reporter: Florin Gheciu >Priority: Trivial > -- This message was sent by Atlassian Jira (v8.3.4#803005)
