Hello,
I am pleased to be calling this vote for the source release of Apache
NiFi Flow Design System 0.2.0.
The source zip, including signatures, etc. can be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/
The Git tag is NIFI-FDS-0.2.0-RC1
The Git commit ID i
Hello Apache NiFi community,
Please find the associated guidance to help those interested in
validating/verifying the Apache NiFi Flow Design System release so they can
vote.
# Download latest KEYS file:
https://dist.apache.org/repos/dist/dev/nifi/KEYS
# Import keys file:
gpg --import KEY
Aaron,
Sorry, late night and I read your previous email too quickly. Bryan is
correct, and I just tested it. In the root pom, I added:
>
>
> org.apache.nifi
> nifi-api
> 1.10.0-SNAPSHOT
>
>
>
One more thing, make sure the on the dependencies stays the
same, meaning nifi-api should still be provided. You don't want to end
up bundling the 1.10.0 nifi-api into your NARs.
On Mon, Jul 22, 2019 at 2:21 PM Bryan Bende wrote:
>
> I think you are correct that you would need to also bump nifi-
I think you are correct that you would need to also bump nifi-mock to
1.10.0-SNAPSHPOT.
An easy way to make sure everything gets set to 1.10.0-SNAPSHOT is to
add a block to the top-level pom of your
services project (the parent pom of the service, service api, and
NARs) and in the dep management
Hi Jeff,
Thanks for the information on the release process.
For the error I'm getting, I started a new custom service with:
mvn archetype:generate -DarchetypeGroupId=org.apache.nifi
-DarchetypeArtifactId=nifi-service-bundle-archetype
-DarchetypeVersion=1.9.2 -DnifiVersion=1.9.2
This provides a sh
I work on migrating a large ESB process to a NiFi flow. This process
contains around 40 events (40 different flowfiles). On the ESB a loosely
coupled pattern was used with the help of JMS queues. In NiFi I can use
ports, but than I need to connect those ports. The canvas soon becomes
messy.
Is the
Hi Hitesh,
>From what you've said I believe that this is actually a Kubernetes issue
and not a problem with the Nifi docker container. As such I've responded to
your Stack Overflow post and hopefully someone with a bit more experience
with Kubernetes will then also be able help a bit more from the
Dear Concern,
I am trying to start apache-nifi on AKS(Azure kubernetes service).
But not able to start, Please find error log below
*replacing target file /opt/nifi/nifi-current/conf/nifi.properties sed:
preserving permissions for ‘/opt/nifi/nifi-current/conf/sedSFiVwC’:
Operation no
