Hi Koji:
I modified the error about PR , and pass the check of nifi . But you known that
the main branch was built to fail , so I think the else errors are not my
problem .
What do you think about that? Thank you very much.
Petter Wang
wangj...@weiresearch.com
From: Koji Kawamura
Date: 20
I believe you are correct Bryan. I hope this information is clarified and
makes it into the documentation!
Now, a new wrinkle: as I tried to learn what is going on by trial and
error, I had 2 or 3 Nodes on the 'view the data' Access Policy, the Cluster
Coordinator/Primary Node and the Node I was u
Mark,
I believe whichever node receives the request from the UI, it will
replicate to the other nodes, and the other nodes will see an incoming
request with two entities (the end user, and the node replicating the
request). Those two entities then need to be authorized to see if they
are allowed t
I observed that only the Cluster Coordinator Node (which also happens to be
the Primary Node) needed to be on the Access Policy, not all Nodes.
More to the point, why do the Node(s) themselves need to be on the policy?
When not Clustered, the machine does not need to be on the policy. Perhaps
this
Hi Mark
One needs to make sure all nodes in your cluster are added to the policy and
not just the cluster coordinator.
--
Arpit
On Mar 20, 2017, at 12:05 PM, Mark Bean
mailto:mark.o.b...@gmail.com>> wrote:
In order to successfully 'List queue', a user must be part of the 'view the
data' acces
In order to successfully 'List queue', a user must be part of the 'view the
data' access policy. Similarly, in order to successfully 'Empty queue', a
user must be part of the 'modify the data'. However, in a Cluster
configuration, it appears the Cluster Coordinator must also be in the
relevant poli
What is the project about? Why should I be interested in it?
[rhetorical questions]
The Announce emails are sent to people not on the developer or user lists.
Most will have no idea what the project is about.
So the e-mails should contain at least brief details of what the
product does, and some
Toivo
I'm not aware of efforts to begin implementing this yet. It will be a
very fundamental change and will likely be made far more complicated
by the on-going flow versioning work and performance improvements
happening. You might wish to delve deep into that flow versioning
feature proposal, J
Sorry, never mind - mvn nifi-nar:provided-nar-dependencies
On March 20, 2017 at 11:24:10, Otto Fowler (ottobackwa...@gmail.com) wrote:
Hi,
How would one actually get the dependency mojo to execute, from say a
processor bundle created by the archetype?
It doesn’t execute during mvn package or m
Hi,
https://cwiki.apache.org/confluence/display/NIFI/Wormhole+Connections
Does anyone working on this?
I am interested to have Wormhole connections to improve flow readability.
Any ideas how to move on?
Thanks
Toivo
--
View this message in context:
http://apache-nifi-developer-list.39713.n7
On 20 March 2017 at 15:47, Bryan Bende wrote:
> Sebb,
>
> Sorry for any confusion. I used the normal announce template that we
> always use, except the paragraph that normally explains what NiFi is:
>
> "Apache NiFi is an easy to use, powerful, and reliable system to
> process and distribute
> dat
Hi,
How would one actually get the dependency mojo to execute, from say a
processor bundle created by the archetype?
It doesn’t execute during mvn package or mvn dependency:tree
Thanks
Otto
Sebb,
Sorry for any confusion. I used the normal announce template that we
always use, except the paragraph that normally explains what NiFi is:
"Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute
data. Apache NiFi was made for dataflow. It supports highly
conf
Hello
The Apache NiFi team would like to announce the release of Apache NiFi
nifi-nar-maven-plugin 1.2.0.
The Apache NiFi NAR Maven Plugin helps to build NiFi Archive bundles
(NARs) to support the class loader isolation model in NiFi.
More details on Apache NiFi can be found here:
https://nifi.a
Hi Peter,
Thank you very much for the JIRA and PR. I really appreciate your contribution!
Posted a comment on the next step, please check the comment in Github:
https://github.com/apache/nifi/pull/1604#pullrequestreview-27793004
Koji
On Mon, Mar 20, 2017 at 5:41 PM, wangj...@weiresearch.com
wr
Hi Koji :
Thank you for your advice .Recently , we have finished the localization
work for nifi which based on branch master .And the localization had chinese
and english configuration . The pull request url :
https://github.com/apache/nifi/pull/1604 ,
the JIRA tickiet url : https://issues.ap
16 matches
Mail list logo
