Re: Create custom content viewer

There are defined UI extension points [1]. One of these is for the content viewer. Here is the standard content viewer [2]. Check out this guide and the referenced examples. Matt [1] https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html#ui-extensions [2] https://github.com/apache/nifi/

Re: Policies for root Process Group.

Daniel, The policy should use the UUID of the root Process Group. If your seeding the authorizations.xml as part of your initial start-up, these policies will be automatically applied to your initial admin if there is an existing flow.xml.gz. If there is no flow.xml.gz, you'll need to define thes

Re: Policies for root Process Group.

Daniel, Unfortunately, there is no way to set this currently. This is ultimately a lifecycle issue. The UUID of the root group may be inherited from a cluster or randomly generated if a node is standalone. From the admin guide: "For a brand new secure flow, providing the "Initial Admin Identity"

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Fluid Design System

Matt. With clear documentation and guides, > contributions > >> on > >> > > the sub-projects can be streamlined and be ensured that the > necessary > >> > > changes are already available on the core project i.e NiFi. One

Re: [VOTE] Establish Fluid Design System, a sub-project of Apache NiFi

+1 On Sun, Mar 11, 2018 at 11:40 PM, Koji Kawamura wrote: > +1 > > On Mon, Mar 12, 2018 at 3:10 AM, Matt Burgess > wrote: > > +1 > > > > On Sun, Mar 11, 2018 at 1:00 PM, Jeff wrote: > >> +1 > >> > >> On Sat, Mar 10, 2018 at 8:42 PM Joe Skora wrote: > >> > >>> +1 > >>> > >>> > >>> On Fri, Mar

Re: Add interrupt option for stopped processors with active threads

There is a PR available for the backend work [1]. It is actively being reviewed. Following that, there is additional work to make the front-end changes [2]. It doesn't look like it's going to make it into 1.6.0. However, it should be in scope for 1.7.0 assuming sufficient review traction for both e

Re: NiFi Versioned Process Group Status Icons

Peter, The status icon for a specific Process Group is hidden until that group is versioned. That icon is positioned next to the group name. For the icons in the status bar and in the bottom of the Process Group, we were ultimately just trying to remain consistent. These reflect the counts of the

Re: [VOTE] Release Apache NiFi 1.6.0

+1 (binding) Release this package as nifi-1.6.0 Executed the release helper and verified new granular restrictions with regards to flow versioning. Thanks for RMing Joe! Matt On Fri, Mar 23, 2018 at 4:12 PM, Michael Moser wrote: > +1 (binding) > > Ran through release helper to verify the rele

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

+1 (binding) Release this package as nifi-1.6.0 - Ran through release help - Verified issued discovered by Andrew Lim in previous RC Thanks for RMing Joe! Matt On Thu, Mar 29, 2018 at 8:36 AM, Aldrin Piri wrote: > +1, binding > > > comments: > > * commit looks correct > * signature and hashes

Re: Firefox - Slower movements when moving around the canvas

I have not had a chance to fully dig in but I upgraded from Firefox 57 to Firefox 59. While there is nothing quantitative behind this Firefox 59 seemed to have better performance. I'll continue investigating and digging through some Firefox tickets to see if there is anything interesting. Additiona

Re: [VOTE] Release Apache NiFi 1.6.0 (RC3)

+1 (binding) Release this package as nifi-1.6.0 - Ran through release help - Verified issued discovered by Andrew Lim in previous RC Thanks for RMing Joe! Matt On Wed, Apr 4, 2018 at 2:01 PM, Pierre Villard wrote: > +1 binding > > - went through the release helper guide > - full build on Mac

Re: Search for Controller Service UUID

Mark, The first doesn't sound like it's been implemented yet. The second sounds like a bug. Feel free to file JIRAs for these issues. Thanks! Matt On Wed, Apr 25, 2018 at 9:22 AM, Mark Bean wrote: > When I search for a Controller Service by UUID using the search on the > toolbar, only processo

Re: status bar counts on a cluster

Hey Mark, Just took a quick glance at the merging logic for global counts and it doesn't appear that we consider varying number of invalid components. Explicit merging logic will need to be added. I went ahead and filed a JIRA for it [1]. Matt [1] https://issues.apache.org/jira/browse/NIFI-5128

Re: [VOTE] Change the name Apache NiFi Fluid Design System to Apache NiFi Flow Design System

+1 (binding) Change the name to Apache NiFi Flow Design System On Fri, May 18, 2018 at 9:30 AM, Rob Moran wrote: > Following positive response discussing the name change of nifi-fds [1], I'd > like to call a vote to officially change the name of the Apache NiFi Fluid > Design System to the Apach

Re: [DISCUSS] First Release of NiFi Flow Design System

Scott, Thanks for offering to RM! I'm happy to help review the PR's for the remaining JIRA's you've identified. Matt On Fri, May 25, 2018 at 1:37 PM, Andy Christianson wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Team, > > > > There has been a lot of great work done on the Ni

Re: [VOTE] Release Apache NiFi Flow Design System 0.1.0

-1 binding Signatures, hashes, etc look right. Build was good and the demo application started up just fine. The demo application did load a little slowly so we may want to file a JIRA to improve this in the future. However, it appears that the version bump only happened in the package.json and n

Re: [VOTE] Release Apache NiFi Flow Design System 0.1.0 RC3

+1 binding Ran through helper guide. Verified signatures, hashes, build, etc. Version strings look better with this RC. Provided other feedback regarding improvements to the demo app during RC1. Thanks for RMing this Scott! Matt On Tue, Jun 12, 2018 at 8:28 AM, Rob Moran wrote: > +1 > > * Ste

Re: [VOTE] Release Apache NiFi MiNiFi 0.5.0 RC2

+1 binding Verified signatures, hashes, build, app, etc. Looks good. Thanks for RMing Jemery! Matt On Sun, Jul 1, 2018 at 1:30 PM, Marc wrote: > +1 binding > > Sorry for sending so late Jeremy, but I did verification late > Fridayjust forgot to send > > Built and ran test flows. Verified

Re: I will contact you with one question.

Hi, A recent commit was introduced [1] which will automatically set the page title to the name of your root process group. This feature has not been included in a release yet so keep an eye on the JIRA and the mailing lists for confirmation when it will be available. Thanks Matt [1] https://iss

Re: [VOTE] Release Apache NiFi 1.7.1

+1 (binding) Verified signatures, hashes, build, etc. Ran into one minor thing that probably warrants a note in the migration guide. The certificates that I used in my cluster previously no longer work. It appears the issue is my fault because the certificates did not have the hostname properly s

Re: Moving UI objects on a parent you don't have access to

to allow > this due to time constraints. I do not object to your proposal to change > this (maybe Matt Gilman feels differently?). If you open a Jira, it should > be doable. > > Andy LoPresto > alopre...@apache.org > *alopresto.apa...@gmail.com * > PGP Fingerprint: 70EC B3E5 9

Re: Moving UI objects on a parent you don't have access to

basis for authorization. As long as we're retaining the primary component check as well, we should be ok to introduce this in a minor version release. Matt On Fri, Jul 27, 2018 at 5:49 PM, Matt Gilman wrote: > Please file the JIRA. I'm definitely not opposed to this change long-term,

Re: JSTL support in nifi-web-ui

Karthik, I'm not sure based on the provided details. But it does look like the core taglib is being used in a couple other places. Specifically, in the provenance page and the built-in docs. Might want to compare how its used there. Hope this helps. Matt On Mon, Jul 30, 2018 at 8:49 AM, Karthik

Re: [VOTE] Release Apache NiFi 1.8.0 (RC3)

+1 Release this package as nifi-1.8.0 Validated build, checksums, etc. Ran various deployment configurations and verified new capabilities. Thanks for RMing Jeff! Matt On Tue, Oct 23, 2018 at 1:56 AM Jeff wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apach

Re: Advanced UI button on Update Attributes

David, If I'm understanding your question for 1 they are in the worksheet.jsp. https://github.com/apache/nifi/blob/98aabf2c50f857efc72fd6f2bfdd9965b97fa195/nifi-nar-bundles/nifi-update-attribute-bundle/nifi-update-attribute-ui/src/main/webapp/WEB-INF/jsp/worksheet.jsp#L156 https://github.com/apac

Re: [VOTE] Release Apache NiFi 1.9.0 (rc2)

+1 (binding) - Verified signature, checksums, etc - Verified integration with an OIDC Provider Thanks for RMing Joe! Matt On Tue, Feb 19, 2019 at 1:38 PM Bryan Bende wrote: > +1 (binding) > > - Verified everything in the release helper > - Ran a cluster and tested some scenarios for auto-load

Re: global and component access policies

Mark, You are correct that this behavior differs from the policies on the components themselves. The behavior there always for overriding the allowed users of an ancestor resource. The policies on the policies themselves are inherited and not overridden. This is noted in the UI since the behavior

Re: [DISCUSS] NiFi and Java 11

Jeff, I think this is a great approach that should help us transition to and in the long run, adopt Java 11. The staggered approach should allow us to address concerns and any issues we may encounter as we go over time. Thanks for putting these together! Matt On Thu, Apr 4, 2019 at 2:19 AM Jeff

Re: [VOTE] Release Apache NiFi 1.9.2 (rc2)

+1 (binding) - Verified signature, checksums, etc - Verified integration with an OIDC Provider - Verified basic secure cluster Thanks for RMing Joe! On Thu, Apr 4, 2019 at 12:11 PM Joe Witt wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > nifi-1.

Re: [VOTE] Release Apache NiFi NAR Maven Plugin 1.3.0

+1 binding Ran through release helper. Noticed one of the changes bumps the maven version to 3.1.1. Does this affect our minimum maven version needed to build? If so, we should be sure to update our readme which still references 3.1.0. Thanks for RMing Bryan! Matt On Thu, May 2, 2019 at 10:49

Re: [VOTE] Release Apache NiFi NAR Maven Plugin 1.3.1

+1 (binding) Release this package as nifi-nar-maven-plugin-1.3.1 Follow helper guide. Cleared local repository while building the maven plugin and nifi. Verified build and resulting artifacts working as expected. Thanks for RMing Bryan! On Thu, May 9, 2019 at 2:52 PM Bryan Bende wrote: > Hello

Re: [VOTE] Release Apache NiFi Registry 0.4.0

+1 (binding) Release this package as nifi-registry-0.4.0 Ran through helper guide. Tested bundle uploading. Verified new functionality and UX. Looks good. Thanks for RMing Bryan! On Thu, May 16, 2019 at 5:36 PM Bryan Bende wrote: > Hello, > > I am pleased to be calling this vote for the source

Re: [DISCUSS] Apache NiFi FDS 0.2.0

Sounds great Scott. Thanks for offering to RM! Matt On Tue, Jul 16, 2019 at 9:32 AM Joe Witt wrote: > Nice - glad to see this moving forward! And always happy to see folks > taking on RM duties! > > Thanks > > On Tue, Jul 16, 2019 at 9:27 AM Scott Aslan wrote: > > > Hello everyone, > > > > I

Re: [VOTE] Release Apache NiFi Flow Design System 0.2.0 (RC2)

+1 (binding) Release this package as nifi-fds-0.2.0 Ran through release helper. Checked out demo app and all looks good. Thanks for RMing Scott! Matt On Wed, Jul 24, 2019 at 7:15 AM Kovacs Andras wrote: > * Verified the signature > * Verified the hashes > * Verified README > * Verified the de

Re: Adding Color to Connections

A couple of other things to note: - Connections can already be gray and dashed when the underlying relationship no longer exists. This condition happens often using any Processor whose connections are dynamic (like RouteOnAttribute). - Also, there is already an option to adjust the z-index of a co

Re: NiFi user authentication via OpenId Connect: token expiry issue

Hemantha, NiFi performs a token request. From that response, NiFi gets the ID token which is included from the 'openid' scope that is specified when we invoke the authorization endpoint. NiFi also requests the 'email' scope which NiFi will use as the user identity. We do obtain the expiration from

Re: [VOTE] Release Apache NiFi Registry 0.5.0

+1 (binding) Ran through helper. Verified recent improvements to ignore case when defining groups from a directory server. Tested other basic operations. Looked great. Thanks for RMing Bryan!! On Wed, Aug 21, 2019 at 2:31 PM Bryan Bende wrote: > Hello, > > I am pleased to be calling this vote

Re: Apache NiFi contributor access

Ganesh.B, I've added you to the contributor list. Please let me know if you have any issues. Thanks Matt On Tue, Sep 3, 2019 at 2:33 AM Ganesh, B (Nokia - IN/Bangalore) < b.gan...@nokia.com> wrote: > Hi, > > > > I would like to get contributor access to Apache Nifi on JIRA. Can you > > please

Re: [ANNOUNCE] New Apache NiFi Committer Rob Fellows

Welcome and congrats Rob! On Wed, Sep 25, 2019 at 10:52 AM Yolanda Davis wrote: > Congratulations Rob! > > > > On Sep 25, 2019, at 10:09 AM, Marc Parisi wrote: > > > > Congrats Rob! > > > >> On Wed, Sep 25, 2019 at 9:59 AM Rob Moran wrote: > >> > >> Thanks for all your work, Rob -- congrats! >

Re: [VOTE] Release Apache NiFi 1.10.0 (rc3)

+1 (binding) Verified signatures, hashes, build, etc. Tested both standalone and clustered and secure and unsecured. Thanks for RMing Joe! Matt On Wed, Oct 30, 2019 at 1:51 PM Adam Taft wrote: > +1 (binding) > > Signatures verified. > Hashes verified. > Tests pass, source builds cleanly. > I

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.7.0 (RC1)

+1 (binding) Ran through release helper. Verified signature, checksums, build, tests, etc. Looks good. Thanks for RMing Arpad! On Fri, Jan 10, 2020 at 3:39 PM Kevin Doran wrote: > +1 (binding) > > Ran through the steps in the release helper guide. Noticed a few > release helper instructions th

Re: [VOTE] Release Apache NiFi 1.11.1 (rc1)

+1 binding Verified signature, hashes, full build, etc. Checked small flow and UI issues addressed in this release. All looked good. Thanks for RMing Joe! On Fri, Jan 31, 2020 at 3:11 PM Joe Witt wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1

Re: NIFI Flow Design System

Glenn, Thanks for your comments. The canvas you've experienced unfortunately has not landed in the Flow Design System yet. It is ultimately destined for there but currently, only the NiFi Registry uses FDS. In time, NiFi will be updated to also use it. At that time, the NiFi canvas should be a com

Re: [VOTE] Release Apache NiFi 1.11.2 (rc1)

+1 (binding) - Check signatures and hashes - Full build - Verified some of the JIRAs addressed in this release Thanks for RMing Joe! On Tue, Feb 18, 2020 at 2:01 PM Matt Burgess wrote: > +1 (binding) ran through release helper and various flows. Thanks Joe > for RM'ing! > > On Fri, Feb 14, 202

Re: additionalDetails.html styles

Hi Russell, Do your additional details have different styles than others bundled by NiFi? Have you tried referencing the component-usage.css stylesheet? There is an example here [1]. Let me know if that helps. [1] https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hbase-bundle/nifi

Re: [VOTE] Release Apache NiFi 1.11.3

+1 binding Ran through release validation steps. Looks great! Thanks for RMing Joe! On Fri, Feb 21, 2020 at 10:21 PM Joe Witt wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > 1.11.3. > > The source zip, including signatures, digests, etc. can be

Re: [VOTE] Release Apache NiFi 1.11.4

+1 (binding) Thanks for RMing Joe! On Fri, Mar 20, 2020 at 6:06 PM M Tien wrote: > +1 (non-binding) > > - Verified checksums, signatures, and commit hash > - Ran build and all tests on OS X > - Deployed secure standalone instance > - Verified the fix was applied to use keystorePassword when key

Re: [DISCUSS] Release Timeline for NiFi 2.0.0-M3

I agree. Including the updated UI and getting some feedback would be great. On Mon, Apr 22, 2024 at 8:50 PM Joe Witt wrote: > Id be a big fan of including the new UI. > > On Mon, Apr 22, 2024 at 5:45 PM Pierre Villard < > pierre.villard...@gmail.com> > wrote: > > > Thanks David, I'm happy to tak

[DISCUSS] UI Contributions

Team, Substantial progress has been made on modernizing the NiFi UI under [1] and [2]. As detailed in the JIRAs, this effort has been largely motivated by moving away from deprecated and unsupported dependencies. As we begin the process to transition to the new UI, we are at a point where any UI c

[DISCUSS] Progress Update on new UI

Team, About a month ago a [DISCUSS] thread was sent regarding the UI updates and requesting that any future contributions target both old and new UIs. Since then there has been substantial progress as we continue to close the gap on feature parity with the old UI. Only a few features remain [1] [2

Re: [DISCUSS] Progress Update on new UI

t. > > Thanks > > On Thu, May 30, 2024 at 11:09 AM Scott Aslan > wrote: > > > Outstanding! The new UI is fun, fast, and fantastic. Gathering feedback > > from the community will be invaluable, and the best way to do this is by > > having them actively us

Re: [DISCUSS] Progress Update on new UI

table > before scrolling but the new UI shows 14 rows. Is there any way we can > make the height of each row a bit smaller to fit more on the screen? > > I do appreciate all the hard work done on the new UI. Well done! > > -- Mike > > > On Thu, May 30, 2024 at 2:33 PM Matt Gilma

Re: Unfinished process

Hey Matt, Thanks for the note. That is the nx daemon that appears to be lingering around. I've filed [1] to investigate and fix going forward. It looks like it would shutdown automatically after 3 hours of inactivity, or you can stop it gracefully using npx nx reset from */Users/mburgess/git/nifi/

Re: [DISCUSS] Updated NiFi Flow Design System

Shane, Thanks for the note. This was exactly what I had in mind as we were unpacking all the changes needed to migrate the various UIs within the repo. Co-locating all of our UIs within the nifi-frontend module gives us the opportunity to share and reuse various components, etc. Further, it gives

Re: [DISCUSS] Updated NiFi Flow Design System

registry. Once that's done, maybe we can > revisit the idea of style and component documentation via Storybook or a > similar library for the shared directory. > > Shane > > On Wed, Aug 21, 2024 at 12:18 PM Matt Gilman > wrote: > > > Shane, > > > > T

Re: Get Processor State with REST API

Which version of Apache NiFi are you using? The endpoints were largely refactored for the 1.0.0 release to better align with the resources used to promote multi-tenancy. The endpoint in 1.0.0 should look like http://:/nifi-api/processors//state Matt On Mon, Nov 7, 2016 at 12:49 AM, yih wrote:

Re: NiFi processor validation

I also agreed these changes make sense. In addition, another approach we could consider that has been discussed in the past [1] is to perform component validation asynchronously. This presents its own challenges but would also be helpful. We should try to avoid calling into user code in any web thr

Re: Question: How could I use Rest api to control a single processor to start or stop .

Younge, Thanks for checking out Apache NiFi. To start or stop a Processor the request would look like this: curl ' http://localhost:8080/nifi-api/processors/62b951cb-0158-1000-169b-13bb56ade28a' -X PUT -H 'Accept-Encoding: gzip, deflate, sdch, br' -H 'Content-Type: application/json' -H 'Accept: a

Re: NIFI 1.0.0 SSL

Jamie, It appears that once you've authenticated the user identity contains spaces between the segments of the DN while the value configured as the initial admin does not. To completely eliminate typos, you could try to copy the value from the user log and paste it into the initial admin identity

Re: [DISCUSS] NiFi 1.1.0 release

I have two items that I would like to wrap up prior to creating an RC for 1.1.0. NIFI-2949 addresses some UX issues around Remote Process Group port configuration. The work is already completed and I will be reviewing it this today. Additionally, following recent interest on the mailing list, I'd l

Re: Permission to list queue?

Joe, You would need read permission to the data policy of the source component. Additionally, any nodes proxying your request would also need this permission. If your clustered this includes the nodes in your cluster as a user request could be replicated through any node with zero-master clusterin

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

+1 Release this package as nifi-1.1.0 Ran through numerous configurations including standalone and clustered in both secure and unsecured mode and all is working as excepted. Matt On Sat, Nov 26, 2016 at 1:11 AM, Joe Witt wrote: > Hello Apache NiFi Community, > > I am pleased to be calling thi

Re: New UI Overview video

Thanks Jenn! The new video is awesome. I just published it to the site. It is live now. Matt On Thu, Dec 1, 2016 at 1:16 PM, Andy LoPresto wrote: > Jenn, > > This is great stuff. Thanks for creating these. We will get them on the > site quickly. > > Andy LoPresto > alopre...@apache.org > *alop

Re: [VOTE] Release Apache NiFi - MiNiFi 0.1.0 (RC1)

+1 (binding) Verified signatures, hashes, build, etc. Exported template of data flow from Apache NiFi. Used conversion utility to construct the minifi config.yml. Ran that data flow send data back to my NiFi instance. All worked as expected. Matt On Thu, Dec 1, 2016 at 12:09 AM, Aldrin Piri wr

Re: Reverse Proxy Template Import Error

Rick, The signature of the endpoint that accepts a template upload has not changed (other than the path). Are you running a NiFi cluster in the trusted environment or is it a standalone instance? Is the issue when you attempt to upload the template or when you attempt to drop the template on your

Re: Reverse Proxy Template Import Error

.v2.runtime.ClassBeanInfoImpl.serializeBody( > ClassBeanInfoImpl.java:344) > ~[jaxb-impl-2.2.3-1.jar:2.2.3] > at > com.sun.xml.bind.v2.runtime.XMLSerializer.childAsXsiType( > XMLSerializer.java:700) > ~[jaxb-impl-2.2.3-1.jar:2.2.3] > at > com.sun.xml.bind.v2.runtime.property.Sin

Re: Reverse Proxy Template Import Error

Awesome. Here's the JIRA [1]. I should have the PR posted shortly. Matt [1] https://issues.apache.org/jira/browse/NIFI-3207 On Thu, Dec 15, 2016 at 12:53 PM, Richard St. John wrote: > I should be able to test tonight. > > On Thu, Dec 15, 2016 at 12:45 PM Matt Gilman >

Re: Reverse Proxy Template Import Error

Rick, Here's my proposed solution for the template upload issue [1]. Please give it a shot behind your proxy. Thanks Matt [1] https://github.com/apache/nifi/pull/1334 On Thu, Dec 15, 2016 at 12:58 PM, Matt Gilman wrote: > Awesome. Here's the JIRA [1]. I should have the PR p

Re: Reverse Proxy Template Import Error

t the changes you made to > address the import template issue. I do not know what other verification > is needed for your PR to be approved, but after building NIFI > 1.2.0-SNAPSHOT with your changes from NIFI-3207, the issue is resolved. > > Thanks. > > Rick. > >

Re: [VOTE] Release Apache NiFi 1.0.1 (RC1)

+1 Release this package as nifi-1.0.1 Verified signature, hashes, etc of artifacts and key functionality in this release. Matt On Fri, Dec 16, 2016 at 2:16 PM, Bryan Bende wrote: > +1 Release this package as nifi-1.0.1 > > - Ran through release helper > - Verified the issues around templates

Re: OCSP validation not happening for cluster servers

Joe, If a server connects through the REST API it should be subject to the same checks as a regular user. Can you provide more details regarding the requests that aren't being checked correctly? Additionally, there was some discussion whether we need the additional checks in the first place as we

Re: OCSP validation not happening for cluster servers

nvalid, and >5. test whether the node can still join the cluster. > > The expectation was that in #5 the node would not be able to join to the > cluster, but it could. > > Whether the OCSP check should be handled by NiFi or Java, it doesn't appear > to be happening. >

Re: OCSP validation not happening for cluster servers

https://issues.apache.org/jira/browse/NIFI-1364 > [2] https://blogs.oracle.com/xuelei/entry/enable_ocsp_checking > > On Mon, Dec 19, 2016 at 5:57 PM, Joe Skora wrote: > > > Thanks, I'll check on the configuration used for the tests and reply back > > here once that

Re: OCSP validation not happening for cluster servers

forward would be to introduce these changes, consolidating where possible, and remove the existing legacy OCSP verification in a PR for NIFI-1364. I'll comment regarding my finding on the JIRA. Matt On Tue, Dec 20, 2016 at 10:36 AM, Matt Gilman wrote: > Joe, > > I believe the JIRA

Re: OCSP validation not happening for cluster servers

the folks trying to test it on our end. > > After these changes will all SSL traffic for the Web UI, REST API, > Site-to-Site, and Clustering support OCSP? > > Thanks, > Joe > > On Wed, Dec 21, 2016 at 3:25 PM, Matt Gilman > wrote: > > > Joe, > > >

Re: [VOTE] Release Apache NiFi 1.1.1 (RC1)

+1 (binding) Release this package as nifi-1.1.1 Verified signature, hashes, and key functionality in this release. Thanks Matt On Thu, Dec 22, 2016 at 9:54 AM, Yolanda Davis wrote: > +1 (non-binding) > > Verified signatures, hashes, README, NOTICE and LICENSE. Built and ran on > OS X (java 1.

Re: [DISCUSS] Idea for visual access control policy application

t;> Thanks for the feedback so far. I don’t want to cut off conversation >> here, I just wanted to see if this was worth exploring further and it seems >> it is. I would love to hear additional input from (among others) Andre Fucs >> de Miranda and Anders Braindahl who have bo

Re: How restart and clear state for listHDFS processor

If you're receiving a 405 I think it's unable to find a matching endpoint for the Action/URL/Content-type/Accepts combination. If you're trying to update an existing Processor you'll want to PUT http://localhost:8080/nifi-api/processors/b0c63454-89a8- 15ef-be22-959bd4a72e5a

Re: How restart and clear state for listHDFS processor

If you do a GET for that processor the response will contain the current revision (clientId + version). When you submit a mutable request, you must have the most up to date revision version, or have the same clientId that successfully made the last modification. This ensures that a given client is

Re: Setting a node as primary?

Joe, Sorry for the confusion regarding the documentation. That should have been updated for the 1.0.0 release. I will make sure this gets addressed before our next release. Thanks Matt On Thu, Feb 9, 2017 at 8:29 AM, Andrew Grande wrote: > Not anymore. The assumption is every node in a cluste

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Registry

+1. I really like this idea. Should ease deployments between instances and facilitate a better UX throughout the lifecycle of a dataflow. Matt On Thu, Feb 9, 2017 at 7:52 AM, Koji Kawamura wrote: > Huge +1! I was excited to read the design documents :) > Agree with flow versioning at ProcessGro

Re: [DISCUSS] Proposal for an Apache NiFi sub-project - NiFi Registry

versioned Processors and > Controller Services, such that I could have SuperWidgetProcessor 1.0 and > SuperWidgetProcessor 1.5 on the same flow? > > On Thu, Feb 9, 2017 at 8:42 AM, Matt Gilman > wrote: > > > +1. I really like this idea. Should ease deployments between instances

Re: [VOTE] Establish Registry, a sub-project of Apache NiFi

+1 binding On Fri, Feb 10, 2017 at 11:47 AM, Marc wrote: > +1 non-binding -- but I think creating a sub project creates a demarcation > point that separates responsibilities in a way that makes sense. > > On Fri, Feb 10, 2017 at 11:40 AM, Bryan Bende wrote: > > > All, > > > > Following a solid

Re: [VOTE] Release Apache NiFi 1.1.2

+1 (binding) Release this package as nifi-1.1.2 On Thu, Feb 16, 2017 at 10:37 PM, Andy LoPresto wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > nifi-1.1.2. > > The source zip, including signatures, digests, etc. can be found at: > https://reposito

Re: [VOTE] Release Apache NiFi 0.7.2

+1 (binding) Release this package as nifi-0.7.2 On Thu, Feb 16, 2017 at 11:42 PM, Andy LoPresto wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > nifi-0.7.2. > > The source zip, including signatures, digests, etc. can be found at: > https://reposito

Re: Access policies

Mark, Adding the user and then granting that user permissions to 'view the user interface' is all that is required for the user to access the UI. If you check out the nifi-user.log you should be able to see which request failed. In the coming 1.2.0 release, we've made the authorization error messa

Re: Testing automation, Deployment in NiFi

Anshuman, You could use any process you'd like. If you prefer to build the flow in the UI you can issues requests to the API to stop/stop the components. Alternatively, you can use the API to perform all actions including creation/modification/removal/start/stop/etc. The UI solely uses the API to

Re: Controller Services tab

Joe, The different scoping of Controller Services was part of the multi-tenant effort. The general idea was to establish points of limited availability to ensure the service usage does not become so broad that updating (including stopping and starting of all things that reference the service) is n

Re: [VOTE] Release Apache NiFi nifi-nar-maven-plugin-1.2.0

+1 Release this package as nifi-nar-maven-plugin-1.2.0 On Tue, Mar 14, 2017 at 12:21 PM, Bryan Bende wrote: > Hello, > > I am pleased to be calling this vote for the source release of Apache > NiFi nifi-nar-maven-plugin-1.2.0. > > The source zip, including signatures, digests, etc. can be found

Re: Old Data Provenance. Even though there is new, it is not showing.

Srini, Looking at the screenshot, it appears that you have a search applied. The criteria have resulted in more than the maximum supported number of results (1000). If you want more recent results, try updating the search criteria to more closely hone in on the desired timeframe. The sorting that

Re: Accessing nifi processgroup simutaneoulsy by multiple users

NiFi executes outside of the context of any given user. User 1 can schedule some components and User 2 can unschedule them assuming both users have permissions to all components in question. These components can be unscheduled whenever the user deems it appropriate. The UI reports various metrics s

Re: UI Javascript error in master?

Joe, Can you check the version of Firefox you are running? This appears to be related to NIFI-3035 [1]. Also, was this a fresh install? Was there any component ids in your query string? Thanks Matt [1] https://issues.apache.org/jira/browse/NIFI-3035 On Fri, Apr 7, 2017 at 9:36 AM, Joe Gresock

Re: UI display problem with policies

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 Fri, Apr 7, 2017 at 8:51 AM, Mark Bean wrote: > On the Global Menu, the item Counters is grayed out because the user is not > on the

Re: UI Javascript error in master?

Thanks. I think I see what's going on here. I'm going to do a little more digging and will likely re-open that ticket. Matt On Fri, Apr 7, 2017 at 9:56 AM, Joe Gresock wrote: > Sorry.. that was supposed to be nifi-canvas-utils.js:415 > > On Fri, Apr 7, 2017 at 1:54 PM, Joe Gresock wrote: > > >

Re: UI display problem with policies

ss counters/modify), but it displays no users despite the > fact that I just added a user. In the Console, the 404 error appears. > Again, this reinforces the notion that the page being displayed is actually > the 'access counters/view' policy and not the indicated 'ac

Re: NiFi property values and line separators

Russell, Are you able to provide steps to replicate the loss of line returns? I've tried with properties that both support EL and not. Can you verify the loss of line returns by viewing your flow.xml.gz? Matt On Tue, Apr 18, 2017 at 6:24 PM, Russell Bateman wrote: > I'm writing a custom proces

Re: Chrome and 1.2.0 (SNAPSHOT)

The official browser support is documented in the User Guide [1]. However, it sounds like you might be hitting a Javascript error. As Bryan mentioned, please verify there isn't anything cached. Once your good there, please check out the Console in the Chrome Dev Tools. Thanks Matt [1] https://ni

Re: Chrome and 1.2.0 (SNAPSHOT)

@ jquery.min.js:2 > > (anonymous function) @ jquery.min.js:2 > > i@ jquery.min.js:2 > > j.fireWith @ jquery.min.js:2 > > A@ jquery.min.js:4 > > (anonymous function) @ jquery.min.js:4 > > > > >

Re: Chrome and 1.2.0 (SNAPSHOT)

Mark, A fix has been pushed to master. Let us know if you run into any other issues. Thanks Matt On Fri, Apr 21, 2017 at 12:35 PM, Matt Gilman wrote: > Thanks. I think we figured out the issue. We've reopened the ticket [1] > where this was introduced. Sorry for the inconvenienc

Re: Chrome and 1.2.0 (SNAPSHOT)

gt; We'll pull it down next week. > > > > On Fri, Apr 21, 2017 at 2:40 PM, Matt Gilman > > wrote: > > > >> Mark, > >> > >> A fix has been pushed to master. Let us know if you run into any other > >> issues. > >> > >>

  1   2   3   4   >