Dan,
I believe the issue (if there is one) would be between Zookeeper and
Curator, but NiFi uses Curator 4.x which is the correct version to use with
ZK 3.5.x.
On Thu, Feb 13, 2020 at 12:28 AM dan young wrote:
> Thank you for your email. Looking at the zookeeper docs, with 3.5.0 it
> looks like
Yes, recreating the PG works but as you say, my concern is loss of state. I
need to maintain the state of the database query tasks to prevent myself from
getting a full reload. Is there a way to preserve the state?
-Original Message-
From: Bryan Bende
Sent: Thursday, February 13, 2020
Hello. I am having an issue when trying to execute a mv on
${absolute.path}${filename} to a destination folder, same filename. My
attributes for aboslute.path and filename are just what i expect - no odd
characters on the front or the back ends. I get a nonzero error status -
not always, but on ab
I'm not sure if this option works for you, but in 1.10.0 there was a
force-commit option added, I think it just labeled as Commit but
basically you should be able to commit even when there are newer
versions in the registry.
So if the new version in registry doesn't have any real changes other
tha
Looks like this change was made in 1.9.0:
https://issues.apache.org/jira/browse/NIFI-5812
On Thu, Feb 13, 2020 at 11:55 AM David Gallagher
wrote:
>
> @Bryan Bende, to add to this it looks like 'All' was an option in 1.8.0 but
> is no longer an option in 1.11.1. This is why it can't be reverted,
@Bryan Bende, to add to this it looks like 'All' was an option in 1.8.0 but is
no longer an option in 1.11.1. This is why it can't be reverted, it seems.
Thanks,
Dave
-Original Message-
From: Bryan Bende
Sent: Thursday, February 13, 2020 10:24 AM
To: users@nifi.apache.org
Subject: Re
Hi Bryan - this is the message I see when I upgrade to 1.11:
Execution Mode Changed From 'ALL' to 'PRIMARY'
-Original Message-
From: Bryan Bende
Sent: Thursday, February 13, 2020 10:24 AM
To: users@nifi.apache.org
Subject: Re: NiFi 1.8.0 to 1.11.1 upgrade issue
Ok so your QA environmen
Ok so your QA environment has been upgraded to 1.11.1 and there is an
existing flow that is now in a conflict state because it says there
are local changes for the new properties, but also says a new version
is available from what was committed to registry from the dev
environment?
Can you provide
Hi Bryan -
The new version of the flow came from a development environment. Thinking back
on it, I upgraded that development environment from 1.8 -> 1.11.1 first and
committed the change described to the 0.2.0 registry. I then upgraded the
registry to 0.5.0, made another change, and committed
Hello,
Can you elaborate on what step 3 means? Where did this new version
come from that was imported to registry?
-Bryan
On Thu, Feb 13, 2020 at 9:11 AM David Gallagher
wrote:
>
> Hi – I’m currently converting our flows from 1.8.0 to 1.11.1, with a parallel
> upgrade from registry 0.2.0 to re
Hi - I'm currently converting our flows from 1.8.0 to 1.11.1, with a parallel
upgrade from registry 0.2.0 to registry 0.5.0. Currently stuck due to this set
of steps:
1. Upgraded registry from 0.2.0 to 0.5.0
2. Upgraded NiFi from 1.8.0 to 1.11.1
3. Imported a new version of a flow to t
11 matches
Mail list logo
