Hello Andy,
Thanks for your support, I have deleted the flow.xmlgz file and restarted
both the nodes. Now the Cluster has been connected after restarting the
nodes.
Thanks,
*Raghava Raju*
Softility, Inc. | E: vbhupathir...@softilityinc.com
On Wed, Nov 6, 2019 at 5:06 AM Andy LoPresto wrote:
>
Hi,
In the Change Version section of NiFi User Guide it states that "a
versioned flow can also be rollbacked to an older version" when using the
NiFi Registry. In the NiFi UI I do not see that option. How do a rollback a
flow to an older version and then make the older version the current
version?
Hello,
A upgrade and rollback are both done through "Change Version", going
forward or backward.
In order to make the current version the latest, this feature is only
available in the newest releases (NiFi 1.10.0 and registry 0.5.0)
where you can "Force Commit".
Thanks,
Bryan
On Wed, Nov 6, 20
Looking at the release notes, I see:
* Apache NiFi can now be built on either Java 8 or Java 11! When built
on Java 8 it can run on Java 8 or Java 11.
The implications of this statement make me ask:
* At https://nifi.apache.org/download.html, how is it built? JDK 11?
* Can I run it using
Releases are built with Java 8 until sometime in the future when we
move to Java 11 as the minimum (likely NiFi 2.0.0).
On Wed, Nov 6, 2019 at 10:58 AM Russell Bateman wrote:
>
> Looking at the release notes, I see:
>
> * Apache NiFi can now be built on either Java 8 or Java 11! When built
>
Joe,
Just to verify what you mean,
You are saying that the line:
flowfile = session.putAttribute(flowfile, "receiveType", "active")
could be added before
session.getProvenanceReporter().receive(...)
to indicate a PULL. Is this correct?
Thanks,
Nissim
On Monday, November 4, 2019,
Nissim
Notionally I am saying that session.getProvenanceReporter().receive(...)
should have an option to call
session.getProvenanceReporter().receive(...,ACTIVE|PASSIVE) and if not
specified it would be UNSPECIFIED.
I dont think this needs to be on the flowfile attribute - it would go
straight to
Joe,
Very nice...
Thanks!
Nissim
On Wednesday, November 6, 2019, 1:05:09 PM EST, Joe Witt
wrote:
Nissim
Notionally I am saying that session.getProvenanceReporter().receive(...)
should have an option to call
session.getProvenanceReporter().receive(...,ACTIVE|PASSIVE) and if not
speci
+1 Joe - this is a good compromise to keep the original API undisturbed.
On Wed, Nov 6, 2019 at 11:05 AM Joe Witt wrote:
> Nissim
>
> Notionally I am saying that session.getProvenanceReporter().receive(...)
> should have an option to call
> session.getProvenanceReporter().receive(...,ACTIVE|PAS
Hi NiFi developer team,
I am a big data admin / developer at medical domain at MD Anderson Cancer
Center. We have been working at data streaming for quite a while. When I do the
use case in medical iot, I can see there are a lot of gaps between current
minifi-nifi interaction, so I would like t
Hello, some developer can verify this:
https://issues.apache.org/jira/browse/NIFI-6853
It is related to the bug I reported a few days ago
NIFI-6800
This is another problem in the StandardProcessSession.java
promptly in the combination of the counters for the event repository
(flowfileEvent
Hi there,
We have two addresses on each of our NiFi cluster hosts. One is externally
facing, which we use to access the UI, and connect to receiving processors
from the wider network. We are trying to configure NiFi to use the internal
network for its cluster traffic. However if I use the internal
Hi Daniel,
Glad to hear about your interest in MiNiFi! MiNiFi's processes and
procedures are not significantly different than those of NiFi, so the
Contributor Guide [1] is a great reference point for how to engage.
As you are likely aware, we have both Java and C++ implementations. Based
on yo
13 matches
Mail list logo
