Hi Mike,
I agree with the approach that enrich provenance events. In order to
do so, we can use several places to embed meta-data:
- FlowFile attributes: automatically mapped to a provenance event, but
as Andy mentioned, we need to be careful not to put sensitive data.
- Transit URI: when I
Hi Milan,
The idea would be the following:
- disconnect the node from the cluster
- go on the ui of the disconnected node and stop the "input" processors
where the data is ingested/received and wait for the all data being on the
node to be processed (this can be scripted). Since the node is
Hi All,
I have 5 node NIFI cluster running in a client environment. We have decided to
keep the running with 4 NIFI cluster node by taking one down.
NIFI is using embedded zookeeper.
Question is: How can we take one of the NIFI out from the cluster. I can simply
remove and stop it but I want
Hi Adam,
Not sure if the unused constant in that class is just a remnant from a move or
refactoring that wasn’t cleaned up, but the header itself is used in
WebUtils.java [1] during request processing to determine the context path. That
method is used in determining the resource path in
Hello all,
I am wondering if there is any intention of using the X-ProxyContextPath header
in the org.apache.nifi.web.api.ApplicationResource class?
The class defines the static:
public static final String PROXY_CONTEXT_PATH_HTTP_HEADER =
"X-ProxyContextPath";
However, it is unused and
Phil,
is there any backpressure being applied to the GetTCP processor?
I.e., is the connection that GetTCP is putting FlowFiles in full?
It sounds like the system starts out fast and then the performance decays
over time? Is that accurate? How long as it fast after a restart?
If there is no
Hey Mike,
I'd suggest waiting for Mark's feedback on this one since he already
reviewed the PR.
I think he is the best one to merge it if nothing else is required ;)
Pierre
2018-05-15 0:55 GMT+02:00 Mike Thomsen :
> https://github.com/apache/nifi/pull/2672
>
> The test
Just to give an update on this in case someone else has the same issue: the
last version of Firefox (60.0) solved the problem.
Pierre
2018-04-04 19:58 GMT+02:00 Pierre Villard :
> OK... that's weird. I also have the same issue when running FF in safe
> mode (with no
hi all,
it should be possible to disable all remote processors groups inside a
Processor group right ?
should we start with a PR for the API ?
Jorge Machado