Access policies

I am attempting to apply Access Policies appropriately. As a very first step, I want to grant a user access to the UI. From the global menu, I chose Users and added the user. Then, again from the global menu, I chose Policies. I added the user to "view the user interface" and "access the

Re: Access policies

r > modify them. Without these permissions, the user can still see the data > flow but they will not be able to see details of those components. > > Matt > > On Fri, Feb 24, 2017 at 12:32 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > > > I am attempting to apply Acce

Re: Access policies

MyOrg" with > no space entered in NiFi. > > Thanks, > > Bryan > > On Fri, Feb 24, 2017 at 12:58 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > > Your description is exactly how I would expect things to work. However, > the > > user is not able to access t

Re: site-to-site configuration

uot;receive data via > site-to-site" with user of the server added. > > Thanks, > > Bryan > > On Thu, Feb 23, 2017 at 12:34 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > > I am attempting to setup secure site-to-site using NiFi 1.1.1. I have > &g

site-to-site configuration

I am attempting to setup secure site-to-site using NiFi 1.1.1. I have secured NiFi, and am able to access the UI securely via HTTPS. I have set the following security-related properties: nifi.sensitive.props.key= nifi.sensitive.props.key.protected=

Re: site-to-site configuration

create a policy first then you can add users. > > Thanks, > > Bryan > > On Thu, Feb 23, 2017 at 1:01 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > > Bryan, > > > > The server is listed on the global policy for "retrieve site-to-site > >

Zookeeper issues at initial Cluster startup

I am attempting to setup a new Cluster with 3 Nodes initially. Each node is reporting zookeeper/curator errors, and the Cluster is not able to connect the Nodes. The error is reported many times per second and is continuous on all Nodes: 2017-02-28 14:22:53,515 ERROR [Curator-Framework-0]

Re: Zookeeper issues at initial Cluster startup

he first followers use to connect > > to the leader, and the second is for leader election. The leader > > election port is only necessary if electionAlg is 1, 2, or 3 > > (default). If electionAlg is 0, then the second port is not necessary. > > If you want to test multiple servers

Bulletins from within a Controller Service

In a Controller Service, bulletins are issued when an exception is thrown in the @OnEnabled method. However, I would like to issue a bulletin from other methods in the CS. in this use case, the CS connects to a socket for a remote lookup service. If the remote service becomes unavailable, it would

Re: List/Empty queue on a Cluster

> 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 <mark.o.b...@gmail.com mark.o.b...@gmail.com>> wrote: > > In order to successfully 'List que

Re: List/Empty queue on a Cluster

from the node that was the cluster > coordinator? > > If so maybe all of your list/clear operations succeeded with only that > node in the policies, but if you went to the UI from another node > maybe it wouldn't work? > > -Bryan > > On Mon, Mar 20, 2017 at 3:53 PM, Ma

List/Empty queue on a Cluster

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

Shutdown of one Node in Cluster

I have a 3-node Cluster with each Node hosting the embedded zookeeper. When one Node is shutdown (and the Node is not the Cluster Coordinator), the Cluster becomes unavailable. The UI indicates "Action cannot be performed because there is currently no Cluster Coordinator elected. The request

Re: Shutdown of one Node in Cluster

one would not want to do this. But when testing, this should be acceptable, yes? On Tue, Apr 11, 2017 at 1:56 PM, Mark Payne <marka...@hotmail.com> wrote: > Mark, > > Are all of your nodes running an embedded ZooKeeper, or only 1 or 2 of > them? > > Thanks > -Mark > &g

Re: Shutdown of one Node in Cluster

already heavy resource > load, so if > your cluster starts getting busy, you'll see far more stable performance > from a standalone > ZooKeeper. > > > > On Apr 11, 2017, at 2:06 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > > > > All 3 nodes are runn

Re: Shutdown of one Node in Cluster

other two nodes listed. > > Thanks > -Mark > > > On Apr 11, 2017, at 2:37 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > > > > Ok, will keep the standalone ZooKeeper in mind. > > > > Back to the original issue, any idea why ZooKeeper went to a PENDING > sta

Documentation for 1.x

I have been asking many questions lately regarding NiFi 1.x because we are in the process of more deliberately evaluating 1.x as it relates to our current production level flows. In the process, I have found the documentation to be incomplete, sometimes incorrect (e.g. typo), contain references to

nifi.templats.directory

In NiFi 1.x (as compared to 0.x), any templates are now stored directly in the flow.xml.gz file. Is that correct? If so, what is the purpose (if any) of the nifi.properties entry for "nifi.templates.directory"? Should this property be deprecated/removed?

Re: nifi.templats.directory

lows us to migrate > templates from 0.x to 1.x. > Otherwise, we would have lost all templates when migrating. > > Thanks > -Mark > > > > On Apr 12, 2017, at 11:40 AM, Mark Bean <mark.o.b...@gmail.com> wrote: > > > > In NiFi 1.x (as compared to 0.x), an

Re: Documentation for 1.x

gt; On Wed, Apr 12, 2017 at 11:54 AM, Mark Bean <mark.o.b...@gmail.com> wrote: > > > I have been asking many questions lately regarding NiFi 1.x because we > are > > in the process of more deliberately evaluating 1.x as it relates to our > > current producti

UI display problem with policies

On the Global Menu, the item Counters is grayed out because the user is not on the 'access counters' policy To to: Global Menu > Policies > access counters/modify Create a new policy (one did not exist yet) Add the user At this point, the Access Policies page correctly shows the user has been

Re: Cluster using Site-to-Site

work > for you? > > Thanks > Joe > > On Apr 14, 2017 1:57 PM, "Mark Bean" <mark.o.b...@gmail.com> wrote: > > > In 0.x, one would point a Remote Process Group (RPG) at the NCM. The NCM > > would then take care of load balancing to the corresponding Input

Re: nifi.templats.directory

at 2:37 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > Mark, > > I stand corrected. The template in ./conf/templates is not added to the > flow.xml.gz on restart. I confirmed this behavior in both 1.1.1 and 1.1.2. > Can you please re-verify? > > These are the steps I

Chrome and 1.2.0 (SNAPSHOT)

I built 1.2.0-SNAPSHOT from master. It does not display on Chrome (version 50.0.2661.94). The splash page comes up, but it goes no further. It displays properly on Firefox (version 31.5.0). This was not a problem with NiFi 1.1.2. Is there a known minimum browser version for NiFi? Is there a

Re: Chrome and 1.2.0 (SNAPSHOT)

ve > > outdated javascript, etc files cached? > > > > Thanks, > > Bryan > > > > On Fri, Apr 21, 2017 at 11:25 AM, Mark Bean <mark.o.b...@gmail.com> > wrote: > > > > > I built 1.2.0-SNAPSHOT from master. It does not display on Chrome > >

Re: Chrome and 1.2.0 (SNAPSHOT)

t;> >> > Hi Mark, >> > >> > To my knowledge there's no reason it shouldn't work in Chrome. Have you >> > tried the "Empty Cache and Hard Reload" option to verify you don't have >> > outdated javascript, etc files cached? >> > >&g

Curator error messages

Occasionally, while testing scenarios on a 3-Node cluster a Node will be removed from the cluster. Sometimes, the log files begin filling with an inordinate amount of repeated messages from the Curator. I'm still trying to track down what instigates this, but most likely it is when one of the 3 ZK

Re: Chrome and 1.2.0 (SNAPSHOT)

at 12:35 PM, Matt Gilman <matt.c.gil...@gmail.com> > wrote: > > > Thanks. I think we figured out the issue. We've reopened the ticket [1] > > where this was introduced. Sorry for the inconvenience. > > > > Matt > > > > [1] https://issues.apache.org

Re: Controller Services tab

ed at the global level. > > > > > > All controller services used by processors are created from context > > > palette and are based on the process group you are in at the given > > > time (the root canvas is the root process group). This is done for > > &g

Policy and UI

We just setup a new cluster. A user has been granted: Global policy to access all policies (read and write) Global policy to access the controller (read) Global policy to view system diagnostics (read) Global policy to view the user interface (read) Admin policy for process group NiFi Flow (read)

Re: UI display problem with policies

On Fri, Apr 7, 2017 at 9:54 AM, Matt Gilman <matt.c.gil...@gmail.com> wrote: > Mark, > > Can you check what browser and version you're using? Also, can you open up > the developer tools and see if there are any client side errors? > > Thanks > > Matt > > On

Cluster using Site-to-Site

In 0.x, one would point a Remote Process Group (RPG) at the NCM. The NCM would then take care of load balancing to the corresponding Input Port on the Nodes. In 1.x, the same behavior is true so long as the RPG points to the Cluster Coordinator. (I believe this is true at least.) Here's the rub.

Re: Chrome and 1.2.0 (SNAPSHOT)

at 3:19 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > Thanks Matt. > We'll pull it down next week. > > On Fri, Apr 21, 2017 at 2:40 PM, Matt Gilman <matt.c.gil...@gmail.com> > wrote: > >> Mark, >> >> A fix has been pushed to master. Let us know i

AuthorizerContext

I am writing a custom authorizer, and I need access to some properties in nifi.properties during the onConfigured method. It is similar to the usage in FileAccessPolicyProvider. In this class, there is a setNiFiProperties method annotated with @AuthorizerContext. Presumably, this annotation causes

Re: AuthorizerContext

ng? > > Matt > > [1] https://github.com/apache/nifi/blob/master/nifi-nar- > bundles/nifi-framework-bundle/nifi-framework/nifi- > authorizer/src/main/java/org/apache/nifi/authorization/ > AuthorizerFactoryBean.java#L311 > > On Thu, Jul 27, 2017 at 1:51 PM, Mark Bean <mark.o

Re: Authorization problems of NiFi secured cluster

This is correct. And, there is an alternative to adding the cluster Nodes as "Node Identity" in the authorizers.xml file. Instead, you can use a legacy authorized-users.xml file specifying the file location/name in the "Legacy Authorized Users File" property. In this file, each cluster Node should

External ZooKeeper

Is there a guide, blog, FAQ or other documentation on setting up a dedicated external ZooKeeper (not the embeddded ZooKeeper) for a NiFi Cluster? Thanks, Mark

Re: nifi.templats.directory

w) they should be persisted to the flow.xml.gz. So, for > instance, if you loaded the flow, > then moved a processor to the left a few pixels that would trigger it to > save the templates to > the flow.xml.gz. > > Thanks > -Mark > > > > On Apr 19, 2017, at 10:27 AM, Mark B

Site-to-Site load balancing

How is load balancing across a cluster performed in Site-to-Site? Is it the responsibility of the Cluster Coordinator to inform the remote site-to-site client which Node to push data to? Is the Node determination simply round-robin? or total per Node FlowFile count or byte count? or based on some

unstable cluster

We have a cluster which is showing signs of instability. The Primary Node and Coordinator are reassigned to different nodes every several minutes. I believe this is due to lack of heartbeat or other coordination. The following error occurs periodically in the nifi-app.log ERROR

Re: unstable cluster

Update: now all 5 nodes, regardless of ZK server, are indicating SUSPENDED -> RECONNECTED. On Thu, May 25, 2017 at 10:23 AM, Mark Bean <mark.o.b...@gmail.com> wrote: > I reduced the number of embedded ZooKeeper servers on the 5-Node NiFi > Cluster from 5 to 3. This has improved t

Re: unstable cluster

is very long. Are these nodes > across a WAN link? > > On Thu, May 25, 2017 at 11:08 AM, Mark Bean <mark.o.b...@gmail.com> wrote: > > Update: now all 5 nodes, regardless of ZK server, are indicating > SUSPENDED > > -> RECONNECTED. > > > > On Thu, May 25, 20

Re: unstable cluster

13:40:07,787; send took 129 millis I will work on setting up an external ZK next, but would still like some insight to what is being observed with the embedded ZK. Thanks, Mark On Wed, May 24, 2017 at 3:57 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > Yes, we are using the embedd

Re: unstable cluster

mparison i'm looking at heartbeat logs from > > another cluster and the times are consistently 1-3 millis for the > > send. Yours above show 100+ms typical with one north of 900ms. Not > > sure how relevant that is but something i noticed. > > > > On Thu, May 25, 2017 at

Re: unstable cluster

ZOOKEEPER-850 > [3] https://issues.apache.org/jira/browse/ZOOKEEPER-1371 > [4] https://issues.apache.org/jira/browse/ZOOKEEPER-2393 > [5] https://issues.apache.org/jira/browse/ZOOKEEPER-2342 > > - Jeff > > On Tue, May 30, 2017 at 8:15 AM Mark Bean <mark.o.b...@gm

Re: unstable cluster

; > > > > >> > > > > I did report a JIRA [1] for upgrading to 3.5.2 or 3.6.0 (just > due > >> to > >> > > > log4j > >> > > > > issues) once it's out and stable, There are issues with the way > >> that > >> > ZK > >

Re: Group button

lard <pierre.villard...@gmail.com > wrote: > It's working fine on master, and I don't remember a JIRA about this but it > could be somehow linked to another one. > > 2017-06-16 19:26 GMT+02:00 Mark Bean <mark.o.b...@gmail.com>: > > > Ok, I discovered that is how

Re: Group button

tion you can press shift and draw a > rectangle on your canvas to make the selection. > > Hope this helps, > Pierre > > 2017-06-16 16:47 GMT+02:00 Mark Bean <mark.o.b...@gmail.com>: > > > The Group button on the Operate Palette is perpetually grayed out. What > >

Group button

The Group button on the Operate Palette is perpetually grayed out. What policy is required to allow its use? And, what is its purpose? I assume it is to group multiple components together as a single selectable component within the UI for doing such things as moving those elements as a single

Re: unstable cluster

gt; clusters and should see good behavior. Even if the system overall is > not under all that high of load if you're seeing garbage collection > pauses that are lengthy and/or frequent it can cause the same high > load effect as far as the JVM is concerned. > > Thanks > Joe &

Fwd: [VOTE] Release Apache NiFi 1.4.0 (RC2)

Hey guys, Has anyone attempted to build 1.4.0-RC2 (or -RC1 for that matter)? I don't see those tags. I don't see them from command line git after doing a pull. I don't see them on the Github website either. I don't even see the commit mentioned in this announcement. And, the link to the commit

Re: [VOTE] Release Apache NiFi 1.4.0 (RC2)

; > Thanks > > On Thu, Sep 28, 2017 at 7:34 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > > Hey guys, > > > > Has anyone attempted to build 1.4.0-RC2 (or -RC1 for that matter)? I > don't > > see those tags. I don't see them from command line git after doing

Re: [CANCEL] [VOTE] Release Apache NiFi 1.4.0

Jeff, All outstanding issues have been resolved/committed, right? Can RC2 get turned around quickly? We were hoping to have an official 1.4.0 release by the end of the week. Thanks, Mark On Mon, Sep 25, 2017 at 2:51 PM, Jeff wrote: > Given the issues discovered today, I

determine if instance is a Cluster Coordinator or Primary Node

Is there a way to get access to Cluster configuration state? Specifically, can a Node determine which Node - or simply "itself" - is the Cluster Coordinator or the Primary Node? Use case: I have a custom authorizer which includes a background thread to re-authorize users and policies in case a

Re: determine if instance is a Cluster Coordinator or Primary Node

that are managed > in NiFi. In this scenario, the users/groups/policies remain consistent and > access decisions are accurate even if one of the nodes receives an update > in your background thread before the others. > > Matt > > On Tue, Aug 29, 2017 at 8:08 AM, Mark Bean <mark.o.b

Re: determine if instance is a Cluster Coordinator or Primary Node

mary or not. > > Then they can annotate a method with @PrimaryNodeStateChange to get > notified when primary node changes. > > -Bryan > > > > On Tue, Aug 29, 2017 at 8:08 AM, Mark Bean <mark.o.b...@gmail.com> wrote: > > Is there a way to get access to Cluster con

Provenance query results in Node disconnect from cluster

We are seeing cases where a user attempts to query provenance on a cluster. One or more Nodes may not respond to the request in a timely manner, and is then subsequently disconnected from the cluster. The nifi-app.log shows log messages similar to: ThreadPoolRequestReplicator Failed to replicate

Re: Provenance query results in Node disconnect from cluster

> > I have answered specific questions below, though, in case they are helpful. > > Thanks > -Mark > > > > On Nov 20, 2017, at 3:25 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > > > > We are seeing cases where a user attempts to query p

Re: [ANNOUNCE] New NiFi PMC member Mike Moser

Congrats Mike!! On Mon, Nov 20, 2017 at 7:17 PM, Corey Flowers wrote: > About time!!! Congrats Mike > > Sent from my iPhone > > > On Nov 20, 2017, at 6:58 PM, Michael Hogue > wrote: > > > > Congratulations, Mike! > >> On Mon, Nov 20,

build failure

I'm getting build failures when I attempt to build the latest master on one environment but not another. The failure was on macOS 10.12.6, maven 3.3.9, java 1.8.0_74. I agree, some of those could (and will be soon) updated. Yet, I was able to build successfully on an AWS EC platform earlier

cluster property not in nifi.properties

It was observed that nifi.cluster.request.replication.claim.timeout property is not in the default nifi.properties file. I assume this property is still relevant (i.e. hasn't been deprecated.) Should it be included in nifi.properties? Thanks, Mark

SSL and Zookeeper

Has anyone setup zookeeper connections for a NiFi Cluster over SSL? We have ZK itself running over SSL. How do we get the NiFi to ZK connections secure? Is this possible? Advice, suggestions and/or documentation greatly appreciated. Thanks, Mark

Cluster behavior when heavily loaded

We have a 6-node cluster using external ZooKeeper. It is heavily loaded, and we are attempting to tune some of the properties to alleviate some observed issues. By "heavily loaded" I mean the graph is large (approx. 3,000 processors) and there is a lot of data in process (approx. 2M

PR AppVeyor build failure

It appears the AppVeyor build failed on my PR [1]. It also appears that it simply timed out after 90 minutes. Is there a way to re-run this check? [1] https://github.com/apache/nifi/pull/2703 Thanks, Mark

Re: API endpoint for /resources

licies for. > > As far as I know, a user would need READ to /resources to make a > request to the end-point. > > Thanks, > > Bryan > > > On Thu, Jun 7, 2018 at 8:13 AM, Mark Bean wrote: > > What information specifically does the Rest API endpoint "/resources&q

API endpoint for /resources

What information specifically does the Rest API endpoint "/resources" provide? Also, a user belongs to every policy, and when hitting that endpoint still receives "No applicable policies could be found. Contact the system administrator." Is the "/resources" endpoint still supported? Thanks, Mark

Re: [DISCUSS] Change of Cluster Flow Inheritance

Great ideas Mark. Another addition for ease/convenience of a node joining a cluster is related to the authorizations.xml and users.xml. In the case of the flow.xml.gz, if the file is missing, it will obtain a copy from the cluster. The same should be true of authorizations.xml and users.xml files,

Re: [DISCUSS] Release candidate timeframe for Apache NiFi 1.7.0

I updated NIFI-4907 to have a fix version of 1.7.0. -Mark On Tue, Jun 5, 2018 at 3:09 PM, Andy LoPresto wrote: > Sending out an update. I am using the following search query to take a > look at what is still outstanding for 1.7.0. Currently I have visibility on > the following issues: > >

validation changes in 1.7.0

Several of our custom processors are not compatible with version 1.7.0. There is a growing pattern of unit test failures due to customValidate() not being executed now where it was being executed in 1.6.0 and prior. I believe there were changes made in 1.7.0 in terms of how validation - and

Re: validation changes in 1.7.0

or hopefully a quick turn-around on 1.7.1 - or even minimally the completion of NIFI-5368 that we could apply to a forked version. Thanks, Mark B. On Tue, Jul 3, 2018 at 10:15 AM Mark Bean wrote: > Mark, > > You're exactly correctly. I discovered the workaround of addi

Re: validation changes in 1.7.0

all referenced services are valid. > > Thanks > -Mark > > > [1] https://issues.apache.org/jira/browse/NIFI-5368 > > > On Jul 3, 2018, at 8:55 AM, Mark Bean mark.o.b...@gmail.com>> wrote: > > This issue is not related to EL. I've tripped ov

Re: validation changes in 1.7.0

> > > component that got removed in some of this refactoring. > > > > > > > > I do see in StandardProcessorTestRunner (the impl of the TestRunner > > > interface) that when run() is called, are still > > > > performing validation as we were previou

site-to-site timeout

It was observed in Apache NiFi 0.x that when the NCM goes down or becomes unavailable, data being sent to the cluster via site-to-site continues to flow to the Nodes for 24 hours. There is a state file NIFI_HOME/conf/state/{RPG-UUID}.peers. When this file becomes > 24 hours old, the site-to-site

Re: site-to-site timeout

it is finally successful. > > Thanks > -Mark > > > > On Jan 8, 2018, at 1:29 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > > > > It was observed in Apache NiFi 0.x that when the NCM goes down or becomes > > unavailable, data being sent to the clust

Empty String in UpdateAttribute

UpdateAttribute supports stateful properties. In doing so, the validator applied to the attributes changes. In the case where stateful properties are not desired, the validator adds StandardValidators.NON_EMPTY_VALIDATOR. This means the "Set Empty String" checkbox cannot be used. One solution is

Re: Empty String in UpdateAttribute

nce of > the > > > code changes. If you would like to write a new JIRA, then I'm sure we > > can > > > restore the "Set Empty String" functionality when not storing > attributes > > in > > > local state. > > > > > >

Bulletins on Processors summary tab

In NiFi 0.x, the Summary/Processors page lists bulletins (if any) in the first column along with 'info'. This is a convenient way to sort the list of processors and find those with active bulletins. However, in 1.x, this feature seems to be missing on the Summary/Processors tab. Is there some

Policies and access to core attributes

In order to use Provenance to view details of a flow file, a user must belong to the 'view the data' policy for a given component(s) along the flow. For example, the lineage graph will show "UNKNOWN" for any component which the user does not possess 'view the data'. Not only can the user not

Re: Upgrading NiFi Registry

same as NiFi... stored in users.xml and > authorizations.xml the conf directory, depending how you configured > everything. So just copying those two files over to the new install. > > -Bryan > > > On Wed, Jun 20, 2018 at 11:13 AM, Mark Bean wrote: > > How does one upgrade the NiFi Regis

Re: [VOTE] Release Apache NiFi 1.7.1

+1 (non-binding) Signature and hashes look good Commit matches Build with contrib-check passes Installed binary and ran trivial flows to verify installation On Sat, Jul 14, 2018 at 3:53 PM Aldrin Piri wrote: > +1, binding > > hashes and signature looked good > full build with contrib-check

Re: [discuss] should we do a nifi 1.7.1 release?

+1 for a 1.7.1 release if it contains a fix for NIFI-5368 [1]. This bug is breaking multiple unit tests on custom processors. [1] https://issues.apache.org/jira/browse/NIFI-5368 On Thu, Jul 5, 2018 at 12:23 PM Joe Witt wrote: > team, > > Wanted to kick off a thread to suggest we do a nifi

Re: [discuss] should we do a nifi 1.7.1 release?

m: Andy LoPresto [mailto:alopre...@apache.org ] > Sent: Friday, July 06, 2018 1:34 AM > To: dev@nifi.apache.org > Subject: Re: [discuss] should we do a nifi 1.7.1 release? > > I’m working on the wildcard cert issue and would be able to put that > > along > > with some other

[DISCUSS] NiFi shared file system

I'd like to start a discussion on making NiFi Clustering more robust. As it is, a Cluster is very beneficial from a management standpoint. A change only needs to be made in one place - any place - and it is replicated across the cluster. However, from a data perspective, the same flexibility is

Re: RAT check failure

ifi-grpc-bundle is not included in any phase of the maven > build. You have probably built nifi-grpc-bundle in the past in your > workspace. > > -- Mike > > > On Sat, Mar 10, 2018 at 12:13 PM, Mark Bean <mark.o.b...@gmail.com> wrote: > > > I attempted to r

RAT check failure

I attempted to run 'mvn -Pcontrib-chewck clean install' prior to submitting a PR. It fails with the following RAT checks. (Note: this occurs on master as well, so it is nothing introduced by my changes.) [INFO] Enabled default license matchers. [INFO] Will parse SCM ignores for exclusions...

penalized MockFlowFile

The MockFlowFile has a method setPenalized() which sets the 'penalized' variable to true. And, the isPenalized() method simply returns the value of 'penalized'. (In the real world, isPenalized() is time-based.) How does one un-penalize a MockFlowFile? I believe an unsetPenalized() method may be

status bar counts on a cluster

On a cluster, the status bar reports 4 invalid processors. However, on some nodes there are actually 6 invalid processors. The extra two processors are invalid because a required configuration file (a property of the processor) does not exist on some nodes. The count on the status bar is not

Search for Controller Service UUID

When I search for a Controller Service by UUID using the search on the toolbar, only processors which reference the service are listed, not the service itself. Similarly, when selecting the UUID from the Bulletin Board, it reports "Error: Unable to find the specified component". Is this by

Re: status bar counts on a cluster

This seems to have slipped through the cracks; I haven't seen a response. Does anyone have input? Thanks, Mark On Fri, Apr 20, 2018 at 10:40 AM, Mark Bean <mark.o.b...@gmail.com> wrote: > On a cluster, the status bar reports 4 invalid processors. However, on > some nodes there ar

Oracle ODBCConnectionPool driver

What driver is required to connect to an Oracle database using the DBCPConnectionPool Controller Service? Will the same driver work for both 11g and 12c databases? Thanks, Mark

Re: Oracle ODBCConnectionPool driver

pretty good on backward compatibility as far as I know. > >> On Tue, Oct 16, 2018 at 11:06 PM Mark Bean wrote: >> >> What driver is required to connect to an Oracle database using the >> DBCPConnectionPool Controller Service? Will the same driver work for both >> 11g and 12c databases? >> >> Thanks, >> Mark >>

Load Balancing

I am trying to understand how the load balancing works in NiFi 1.8.0. I have a 2-node Cluster. I set an UpdateAttribute to set the value of a property, "balancer", to either 0 or 1. I am using stateful EL for this: ${getStateValue('balancer'):plus(1):mod(2)}. The connection for the output of the

zero downtime upgrade to 1.8.0

I attempted to upgrade a 3-node Cluster from 1.6.0 to 1.8.0. The process I used was to configure 1.8.0 on all Nodes. Then, one Node at a time, shutdown the 1.6.0 and startup the 1.8.0 version. For the first Node, I copied the flow.xml.gz from the previous 1.6.0 installation. (The

Re: zero downtime upgrade to 1.8.0

ou'd need to give yourself in > that case. Have you already looked there? > > And finally, hard refresh to clear cache is also a possible path > > Thanks > On Fri, Nov 2, 2018 at 12:26 PM Mark Bean wrote: > > > > I attempted to upgrade a 3-node Cluster from 1

Re: [DISCUSS] Extension Registry

designed > against specific components that come from certain nars for which we > know the precise coordinates. When importing flows that depend on > these the system will be able to automatically acquire all that it > needs. > > Thanks > On Tue, Nov 13, 2018 at 12:57 PM Mark B

Re: [DISCUSS] Extension Registry

I would like to see a "group" capability in the Registry for NAR bundles. Then, users can create their own customized grouping of relevant NARs. Managing bundles one at a time will become tedious. Thanks, Mark On Tue, Nov 13, 2018 at 12:48 PM Joe Witt wrote: > Sivaprasanna - yes absolutely.

Controllser Service validation

Scenario: We have a custom Controller Service which was deprecated in favor of its replacement (also custom.) The original CS extends the new CS, and contains just a single method: customValidate. This remained intact to log a message saying "Don't use me.. use the new one." When NiFi was

initial component access policies

When NiFi is started for the first time, the Component Access Policies are not populated even for the Initial Admin or for legacy DFM_ROLE users in authorized-users.xml file.That is, not unless a flow.xml.gz file exists. The fact that the admin user does not have access to these policies has led

Re: initial component access policies

eFlow() method above which tries to > read the flow.xml.gz from disk, using the location from nifi.properties. > > > > On Apr 2, 2019, at 9:57 PM, Mark Bean wrote: > > > > When NiFi is started for the first time, the Component Access Policies > are > > not popul

global and component access policies

There is a global level access policy for 'access all policies' (view and modify). These access policies apply to components (e.g. processor) as well as the controller. Even if a user is explicitly excluded from the component level access policy 'view/modify the policies', the user still has

  1   2   3   >