Re: UI improvements/configuration

[Matt Gilman]

Russell,

Thanks for the feedback.

Specifically regarding the Navigate and Operate pallet, those settings are
saved to your browsers local storage. That is scoped to a specific URL
origin which considers the scheme, host, and port. If you're accessing a
NiFi instance as the same origin, it should remember the docked state of
each. That docked state will be retained for up to two days so as long as
you're accessing your NiFi UI at least once every two days it should
remember. If you're seeing differing behavior please file a JIRA so we can
further investigate.

Thanks

Matt

On Sat, Sep 21, 2024 at 11:09 AM Russell Bateman 
wrote:

> As others suggest UI extensions and other improvements, I have just a
> few usability concerns. I find the UI tedious to use and would like to
> suggest...
>
>   * The ability to configure the two pallets to be collapsed when the UI
> comes up, or remember how they were.
>   * An "undo" ability, perhaps of only the last /n/ accomplishments; for
> me, just the very last change would be marvelous.
>   * The ability to turn off all the confirmation alerts. For example,
> when emptying queues, a person who knows he or she was doing it on
> purpose should not have to confirm that the queue was emptied, okay
> thank you very much, but will just see the queue go to Queued: 0.
>
> These are primitive suggestions--I don't claim to be a UI or UX guy--I
> have accumulated over more than 8 years of writing custom processors
> and, somewhat less, as a user of the UI. The real users of the UI are a
> "cousin" team and they would like to see these and more besides.
>
> Thanks for the Registry. Templates were a crucial need from the early
> days when they appeared. Not to complain, Apache NiFi is an amazing,
> rocking tool.
>
> Russ

Re: Options for UI extensions

[Matt Gilman]

Within the NiFi codebase we only have a single example of a content viewer
that is loaded at runtime using the extension point I described here. That
is the Standard Content Viewer. It can be found here [1]. At startup, NiFi
will discover files that meet the following criteria [2] similar to how
other extensions are discovered using Java SPI. In my last response, I
mentioned that the contract is largely unchanged when compared to the 1.x
baseline. This is one of those differences and will be discussed in the
migration guide for 2.0.0-M5 when that release happens. The
nifi-content-viewer file now contains a listing of content types
categorized by a display name that the user will see in the base Content
Viewer.

Regarding the slide panel, that doesn't sound like an "extension point" but
rather a new capability that could be contributed. For a UI "extension" it
would be something to allow a developer to provide a UI that we load into
the NiFi UI. Typically these would also include APIs or Controllers that
integrate with a contract that the NiFi Framework supports for that
"extension point". For instance, in this content viewer example NiFi offers
the ContentAccess API for accessing content which is then used in an
endpoint supporting Standard Content Viewer UI.

Let me know if you have further questions.

Matt

[1]
https://github.com/apache/nifi/tree/main/nifi-extension-bundles/nifi-standard-bundle/nifi-standard-content-viewer
[2]
https://github.com/apache/nifi/blob/main/nifi-extension-bundles/nifi-standard-bundle/nifi-standard-content-viewer/src/main/webapp/META-INF/nifi-content-viewer
[3]
https://github.com/apache/nifi/blob/main/nifi-extension-bundles/nifi-standard-bundle/nifi-standard-content-viewer/src/main/java/org/apache/nifi/web/controller/StandardContentViewerController.java#L67

On Sat, Sep 21, 2024 at 11:07 AM Mark Bean  wrote:

> For clarification, previously we were unpacking the WAR - simply by
> unzipping it using a plugin - and then adding and in some cases replacing
> JSP files. Then, the WAR was recreated (again, just zipping into a .war
> file). Admittedly, this is not a desirable approach which is why I was
> asking about natural extension points.
>
> I will take another look based on your suggestions. It's not
> immediately obvious to me how or where a custom WAR would be recognized by
> the UI. Do you have an example to point to, or a class/interface that is
> the hook for the extension?
>
> Regarding the content viewer, we have a customized viewer with a slide
> panel that shows FF details/attributes alongside the content pane. I'm not
> sure this type of extension is what you have in mind or is possible.
> Rather, I think you are saying that a custom viewer would support the
> content pane itself. Is that correct? If the slide panel isn't an
> appropriate extension, at least this feature of all mentioned seems like an
> appropriate contribution to the base content viewer.
>
> Thanks,
> Mark
>
>
>
> On Sat, Sep 21, 2024 at 10:47 AM Matt Gilman 
> wrote:
>
> > Mark,
> >
> > There are "extension points" in the UI for Advanced UIs and Content
> > Viewers. The capability is largely unchanged from the 1.x baseline in
> that
> > WARs are discovered at runtime and are associated with specific
> components
> > or content types. The UIs themselves do not need to be part of the
> > nifi-frontend module. This project just allows all UIs provided by Apache
> > NiFi itself to share a common set of dependencies, reuse components,
> > styles, etc. But any WAR that meets the criteria (the same criteria as
> the
> > 1.x baseline) will be deployed and the extension UIs will be available in
> > the UI.
> >
> > There are no further optimizations for the banner text. It is intended to
> > allow a text string to be configured. There is also no ability to
> provide a
> > custom logo.
> >
> > The Content Viewer is designed to support viewing a single piece of
> > content. This is any piece of content in a Queue or referenced as
> > input/output of a Provenance Event. If in your scenario the text/metadata
> > and image were within the same piece of content it would be doable
> through
> > this extension point. If not, a new extension concept may be needed if
> the
> > scenario could be generalized and would be helpful in other cases. If
> not,
> > you could fork the codebase and implement purpose built UIs for your
> > specific use cases.
> >
> > It's not clear based on your last paragraph how the UIs were previously
> > being modified with a custom build. If you mean that you were manually
> > modifying the UI components and rebuilding, that is still possible in 2.x
>

Re: Options for UI extensions

[Matt Gilman]

Mark,

There are "extension points" in the UI for Advanced UIs and Content
Viewers. The capability is largely unchanged from the 1.x baseline in that
WARs are discovered at runtime and are associated with specific components
or content types. The UIs themselves do not need to be part of the
nifi-frontend module. This project just allows all UIs provided by Apache
NiFi itself to share a common set of dependencies, reuse components,
styles, etc. But any WAR that meets the criteria (the same criteria as the
1.x baseline) will be deployed and the extension UIs will be available in
the UI.

There are no further optimizations for the banner text. It is intended to
allow a text string to be configured. There is also no ability to provide a
custom logo.

The Content Viewer is designed to support viewing a single piece of
content. This is any piece of content in a Queue or referenced as
input/output of a Provenance Event. If in your scenario the text/metadata
and image were within the same piece of content it would be doable through
this extension point. If not, a new extension concept may be needed if the
scenario could be generalized and would be helpful in other cases. If not,
you could fork the codebase and implement purpose built UIs for your
specific use cases.

It's not clear based on your last paragraph how the UIs were previously
being modified with a custom build. If you mean that you were manually
modifying the UI components and rebuilding, that is still possible in 2.x
it's just the UIs were built differently.

Matt

On Sat, Sep 21, 2024 at 10:16 AM Mark Bean  wrote:

> I am investigating the options available (or not) for extending elements of
> the UI. I have three specific examples, but the question is also the
> general case: can the UI be extended by custom visualization and/or
> behavior.
>
> Three examples are header, footer and content viewer. It is desirable to
> have decoration added to the otherwise available property
> "nifi.ui.banner.text" (nifi.properties.) For example, users may want to
> change the text color, background color or display multi-line text. As for
> the header, it would be interesting to be able to change the NiFi logo to a
> company logo or instance/cluster-specific graphic.
>
> Lastly, the content viewer seems an ideal place for extension as some file
> formats may have different display requirements; consider the case of a mix
> of text (metadata) and image. Moreover, the format itself may be
> proprietary so the details of a viewer cannot be contributed back to Apache
> NiFi.
>
> For NiFi 1.x, it was possible to inject JSP for options such as these - not
> trivial, but possible with a custom build. For NiFI 2.x, the nifi-ui WAR
> packaging does not appear to be as easily modified even in a custom build.
>
> Thanks in advance for guidance or suggestions.
>
> -Mark
>

Re: [DISCUSS] Updated NiFi Flow Design System

[Matt Gilman]

Sounds like a plan.

Thanks Shane!

Matt

On Wed, Aug 28, 2024 at 7:44 PM Shane Ardell 
wrote:

> Perfect, Matt. Thanks for chiming in. Since what I described aligns with
> the direction you and others had in mind, I'll gladly create some Jiras and
> start the effort to migrate nifi-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,
> >
> > 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 us a single place for managing all front end dependencies. In time,
> > all UIs will be migrated and updated such that they are on common and
> > current versions of dependencies. I am currently in the process of
> > migrating our content viewers into nifi-frontend following this model.
> >
> > Matt
> >
> > On Wed, Aug 21, 2024 at 10:59 AM Shane Ardell 
> > wrote:
> >
> > > Team,
> > >
> > > As work continues with the new NiFi UI as well as the Jolt Transform
> UI,
> > it
> > > has come to my attention that these two interfaces utilize a library of
> > > shared Angular components, directives, pipes, etc., located at
> > > `nifi-frontend/src/main/frontend/libs/shared`. In my opinion, this
> shared
> > > library seems to be the successor to nifi-fds, which is not utilized by
> > > either of the new interfaces and doesn't seem to be actively
> maintained.
> > If
> > > others feel the same, I think we should discuss how to move forward
> with
> > > eventually removing nifi-fds as a dependency and possibly
> incorporating a
> > > library like Storybook [1] to provide documentation for the new design
> > > system.
> > >
> > > The only hurdle I see to removing nifi-fds would be the fact that
> > > nifi-registry still depends on it. In order to resolve this, we would
> > need
> > > to update nifi-registry to the latest version of Angular and refactor
> the
> > > application to utilize this new shared library.
> > >
> > > What does everyone think?
> > >
> > > Shane
> > >
> > > [1] https://nx.dev/recipes/storybook/overview-angular
> > >
> >
>

Re: [DISCUSS] Updated NiFi Flow Design System

[Matt Gilman]

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 us a single place for managing all front end dependencies. In time,
all UIs will be migrated and updated such that they are on common and
current versions of dependencies. I am currently in the process of
migrating our content viewers into nifi-frontend following this model.

Matt

On Wed, Aug 21, 2024 at 10:59 AM Shane Ardell 
wrote:

> Team,
>
> As work continues with the new NiFi UI as well as the Jolt Transform UI, it
> has come to my attention that these two interfaces utilize a library of
> shared Angular components, directives, pipes, etc., located at
> `nifi-frontend/src/main/frontend/libs/shared`. In my opinion, this shared
> library seems to be the successor to nifi-fds, which is not utilized by
> either of the new interfaces and doesn't seem to be actively maintained. If
> others feel the same, I think we should discuss how to move forward with
> eventually removing nifi-fds as a dependency and possibly incorporating a
> library like Storybook [1] to provide documentation for the new design
> system.
>
> The only hurdle I see to removing nifi-fds would be the fact that
> nifi-registry still depends on it. In order to resolve this, we would need
> to update nifi-registry to the latest version of Angular and refactor the
> application to utilize this new shared library.
>
> What does everyone think?
>
> Shane
>
> [1] https://nx.dev/recipes/storybook/overview-angular
>

Re: Unfinished process

[Matt Gilman]

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/nifi-frontend/target/frontend-working-directory*,
or simply kill it.

[1] https://issues.apache.org/jira/browse/NIFI-13385

On Mon, Jun 10, 2024 at 7:26 PM Matt Burgess  wrote:

> I just built from the latest main and haven't run it yet but I still have a
> running process many minutes later:
>
>   503 19756 1   0  6:12PM ?? 0:02.10
>
> /Users/mburgess/git/nifi/nifi-frontend/target/frontend-working-directory/node/node
>
> /Users/mburgess/git/nifi/nifi-frontend/target/frontend-working-directory/node_modules/nx/src/daemon/server/start.js
>   503 32716  8641   0  7:23PM ttys0010:00.00 grep -i nifi
>
> Is there something I need to do?
>
> Thanks,
> Matt
>

Re: [DISCUSS] Progress Update on new UI

[Matt Gilman]

Thanks for the note Mike!

JIRA tickets are probably the best way to track items. We are closely
monitoring [1]. New sub tasks can be filed there. Though also happy to
respond on the mailing list or Slack as well.

I've filed [2] for the table density request.

[1] https://issues.apache.org/jira/browse/NIFI-12400
[2] https://issues.apache.org/jira/browse/NIFI-13331

On Thu, May 30, 2024 at 5:24 PM Michael Moser  wrote:

> Would we prefer Jira tickets or dev emails to discuss design of the new UI?
>
> For example: On the Summary page the old UI could show 25 rows in the 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 Gilman 
> wrote:
>
> > Joe,
> >
> > Thanks for mentioning the documentation. I filed something yesterday [1]
> to
> > capture these efforts.
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-13314
> >
> > On Thu, May 30, 2024 at 2:28 PM Joe Witt  wrote:
> >
> > > Thanks Matt - this path makes sense to me.  I've been using the new ui
> > > exclusively for the past couple of months and now with the improvements
> > and
> > > gaps covered I think it is the perfect time to go to it exclusively.
> We
> > > give at least one milestone release.  We gather feedback/fix things.
> > Then
> > > we launch 2.0!
> > >
> > > Big thanks to all those who contributed to the new UI both in coding as
> > > well as feedback.
> > >
> > > One other thing worth tackling over time is updating documentation
> > imagery
> > > to leverage the new UI but that is something a large group of people
> can
> > > contribute to and much easier when the new UI is what is in use by
> > default.
> > >
> > > 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 use the new UI.
> > > >
> > > > On Thu, May 30, 2024 at 12:37 PM Matt Gilman <
> matt.c.gil...@gmail.com>
> > > > wrote:
> > > >
> > > > > 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]
> > [3]
> > > > [4].
> > > > >
> > > > > The updated UI was included in the most recent 2.0.0-M3 release [5]
> > > > > alongside the old UI. Since then we've received lots of helpful
> > > feedback
> > > > > and all reported bugs and differences from the existing UI have
> been
> > > > > addressed. A new JIRA has been filed [6] to remove the old UI and
> > > install
> > > > > the new UI as the default. This will be a great step forward to be
> > able
> > > > to
> > > > > move away from some frameworks that are no longer officially
> > supported
> > > > [7].
> > > > > When 2.0.0-M4 is released it will only contain the new UI. Until
> then
> > > > > please continue to provide any feedback.
> > > > >
> > > > > Additional work has begun that will establish a good path forward
> on
> > > > > modernizing the remaining UIs within NiFi (documentation, data
> > viewers,
> > > > > custom UIs, etc) that also have outdated/unsupported dependencies.
> As
> > > we
> > > > > continue to make progress on the remaining features, work will
> begin
> > to
> > > > > start modernizing these other UIs.
> > > > >
> > > > > Matt
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/NIFI-13316
> > > > > [2] https://issues.apache.org/jira/browse/NIFI-13317
> > > > > [3] https://issues.apache.org/jira/browse/NIFI-13318
> > > > > [4] https://issues.apache.org/jira/browse/NIFI-13319
> > > > > [5]
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3
> > > > > [6] https://issues.apache.org/jira/browse/NIFI-13313
> > > > > [7] https://issues.apache.org/jira/browse/NIFI-11481
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] Progress Update on new UI

[Matt Gilman]

Joe,

Thanks for mentioning the documentation. I filed something yesterday [1] to
capture these efforts.

[1] https://issues.apache.org/jira/browse/NIFI-13314

On Thu, May 30, 2024 at 2:28 PM Joe Witt  wrote:

> Thanks Matt - this path makes sense to me.  I've been using the new ui
> exclusively for the past couple of months and now with the improvements and
> gaps covered I think it is the perfect time to go to it exclusively.  We
> give at least one milestone release.  We gather feedback/fix things.  Then
> we launch 2.0!
>
> Big thanks to all those who contributed to the new UI both in coding as
> well as feedback.
>
> One other thing worth tackling over time is updating documentation imagery
> to leverage the new UI but that is something a large group of people can
> contribute to and much easier when the new UI is what is in use by default.
>
> 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 use the new UI.
> >
> > On Thu, May 30, 2024 at 12:37 PM Matt Gilman 
> > wrote:
> >
> > > 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] [3]
> > [4].
> > >
> > > The updated UI was included in the most recent 2.0.0-M3 release [5]
> > > alongside the old UI. Since then we've received lots of helpful
> feedback
> > > and all reported bugs and differences from the existing UI have been
> > > addressed. A new JIRA has been filed [6] to remove the old UI and
> install
> > > the new UI as the default. This will be a great step forward to be able
> > to
> > > move away from some frameworks that are no longer officially supported
> > [7].
> > > When 2.0.0-M4 is released it will only contain the new UI. Until then
> > > please continue to provide any feedback.
> > >
> > > Additional work has begun that will establish a good path forward on
> > > modernizing the remaining UIs within NiFi (documentation, data viewers,
> > > custom UIs, etc) that also have outdated/unsupported dependencies. As
> we
> > > continue to make progress on the remaining features, work will begin to
> > > start modernizing these other UIs.
> > >
> > > Matt
> > >
> > > [1] https://issues.apache.org/jira/browse/NIFI-13316
> > > [2] https://issues.apache.org/jira/browse/NIFI-13317
> > > [3] https://issues.apache.org/jira/browse/NIFI-13318
> > > [4] https://issues.apache.org/jira/browse/NIFI-13319
> > > [5]
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3
> > > [6] https://issues.apache.org/jira/browse/NIFI-13313
> > > [7] https://issues.apache.org/jira/browse/NIFI-11481
> > >
> >
>

[DISCUSS] Progress Update on new UI

[Matt Gilman]

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] [3] [4].

The updated UI was included in the most recent 2.0.0-M3 release [5]
alongside the old UI. Since then we've received lots of helpful feedback
and all reported bugs and differences from the existing UI have been
addressed. A new JIRA has been filed [6] to remove the old UI and install
the new UI as the default. This will be a great step forward to be able to
move away from some frameworks that are no longer officially supported [7].
When 2.0.0-M4 is released it will only contain the new UI. Until then
please continue to provide any feedback.

Additional work has begun that will establish a good path forward on
modernizing the remaining UIs within NiFi (documentation, data viewers,
custom UIs, etc) that also have outdated/unsupported dependencies. As we
continue to make progress on the remaining features, work will begin to
start modernizing these other UIs.

Matt

[1] https://issues.apache.org/jira/browse/NIFI-13316
[2] https://issues.apache.org/jira/browse/NIFI-13317
[3] https://issues.apache.org/jira/browse/NIFI-13318
[4] https://issues.apache.org/jira/browse/NIFI-13319
[5]
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M3
[6] https://issues.apache.org/jira/browse/NIFI-13313
[7] https://issues.apache.org/jira/browse/NIFI-11481

[DISCUSS] UI Contributions

[Matt Gilman]

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
contributions should target both the new UI and the existing UI. We've
updated the PR template detailing this and the README for the new UI [3] to
help introduce folks making UI contributions to the layout of the
repository. It discusses the steps needed to build NiFi with the new UI
included and how to access it.

Happy to discuss any questions folks may have.

Matt

[1] https://issues.apache.org/jira/browse/NIFI-11481
[2] https://issues.apache.org/jira/browse/NIFI-12400
[3] https://github.com/apache/nifi/pull/8693

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

[Matt Gilman]

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 take care of a 1.26 release at the same time.
> >
> > Regarding the M3 release, should the new UI be included and instructions
> > given on how to access it to start collecting feedback? I'm under the
> > impression that almost all of the work has been done, no?
> >
> > Thanks,
> > Pierre
> >
> > Le mar. 23 avr. 2024, 02:03, David Handermann <
> exceptionfact...@apache.org
> > >
> > a écrit :
> >
> > > Team,
> > >
> > > We are approaching 300 Jira issues resolved for version 2.0.0-M3 [1],
> > > including a number of important dependency upgrades and Python
> > > framework improvements.
> > >
> > > There are several open pull requests that are getting close to
> > > completion, which should be possible to include in an upcoming release
> > > version. There is also a significant pull request [2] for NIFI-12998
> > > [3] that includes some important changes to module directory
> > > hierarchy, providing a clearer distinction between framework and
> > > extensions, and implementing significant cleanup of dependency
> > > declarations across the repository.
> > >
> > > With these changes in view, we should be ready for another milestone
> > > release soon after merging the above pull request.
> > >
> > > Another milestone release seems to be the best course of action for
> > > now, providing the opportunity for additional review and testing
> > > before a full 2.0.0 release version.
> > >
> > > I would be glad to handle Release Manager responsibilities for
> > > 2.0.0-M3 when things are ready.
> > >
> > > Regards,
> > > David Handermann
> > >
> > > [1]
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20NIFI%20AND%20fixVersion%20%3D%202.0.0-M3
> > > [2] https://github.com/apache/nifi/pull/8677
> > > [3] https://issues.apache.org/jira/browse/NIFI-12998
> > >
> >
>

Re: Cannot build in order to submit PR

[Matt Gilman]

Lucas,

The issue with the static analysis in that PR is the same issue that
someone else ran into earlier today. We're still trying to track it down as
it's seemingly sporadic. I've triggered that job to re-run and it is not an
issue with your PR.

Dan,

We did introduce this new UI behind a profile that is not active by
default. When the profile is not active, the new UI is not included in the
built NiFi assembly. It does, however, build it. We'll update the build so
that it doesn't even build it unless the profile is active. In the meantime
in order to unblock your work, I think you should be able to use mvn -pl
exclude building it locally. Longer term, once the new UI is ready you will
need a system that supports Node.js 20 (the current LTS version) [1].

Matt

[1]  https://github.com/nodejs/release

On Mon, Nov 27, 2023 at 4:07 PM Dan S  wrote:

> Matt,
> Is there a way I can skip that part of the build as my changes have nothing
> to do with the UI.
>
> On Mon, Nov 27, 2023 at 3:55 PM Dan S  wrote:
>
> > Matt,
> > After running mvn clean install in
> >
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend
> > I see the following additional log messages:
> >
> > [INFO]
> >>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node:
> >> /lib64/libm.so.6: version `GLIBC_2.27' not found (required by
> >>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node)
> >> [INFO]
> >>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node:
> >> /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by
> >>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node)
> >> [INFO]
> >>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node:
> >> /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by
> >>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node)
> >> [INFO]
> >>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node:
> >> /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by
> >>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node)
> >> [INFO]
> >>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node:
> >> /lib64/libc.so.6: version `GLIBC_2.28' not found (required by
> >>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node)
> >> [INFO]
> >>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node:
> >> /lib64/libc.so.6: version `GLIBC_2.25' not found (required by
> >>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node)
> >
> >
> > On Mon, Nov 27, 2023 at 3:47 PM Dan S  wrote:
> >
> >> Based on command hostnamectl  I am running on
> >>  Operating System: CentOS Linux 7 (Core)
> >>  CPE OS Name: cpe:/o:centos:centos:7
> >>   Kernel: Linux 3.10.0-1160.90.1.el7.x86_64
> >>   Architecture: x86-64
> >>
> >> It seems the problem is that I do not have GLIBC_2.25 installed.
> >> Apparently though from this forum
> >> <https://forums.centos.org/viewtopic.php?t=73511> I see it is not a
> good
> >> idea to upgrade it.
> >> Please advise.
> >>
> >>
> >> On Mon, Nov 27, 2023 at 3:35 PM Matt Gilman 
> >> wrote:
> >>
> >>> Dan,
> >>>
> >>> Thanks for the response. What kind of system are you building on? I
> &

Re: Cannot build in order to submit PR

[Matt Gilman]

Dan,

Thanks for the response. What kind of system are you building on? I wonder
if there is some incompatibility between the OS and the newer version of
node being used. You should be able to attempt to build
/home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend
directly to focus on the problematic part of the build and save a little
bit of time.

Thanks

On Mon, Nov 27, 2023 at 2:50 PM Dan S  wrote:

> Matt,
>  I reran and this is the message I see before the reactor reports the
> summary
> [INFO]
>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node:
> /lib64/libc.so.6: version `GLIBC_2.25' not found (required by
>
> /home/dystieg/git/NIFI-FORK/nifi/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/target/frontend-working-directory/node/node)
>
> And this is the message I see afterwards:
>
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time:  54:03 min
> [INFO] Finished at: 2023-11-27T19:32:58Z
> [INFO]
> 
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.14.2:npm (npm-install) on
> project nifi-web-frontend: Failed to run task: 'npm run ci' failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1) -> [Help 1]
>
>
>
> On Mon, Nov 27, 2023 at 1:34 PM Matt Gilman 
> wrote:
>
> > Hi Dan,
> >
> > We did land an effort that introduces the beginnings of a new UI [1]. I
> > never ran into this and the GitHub CI for the PR ran successfully but
> > someone else had an issue earlier today too. The actual error should be
> > reported above the summary at the bottom of your build output. Can you
> > please check for those details and see if re-running the build helps?
> We'd
> > like to run down if there are any issues here so others don't run into
> them
> > too.
> >
> > Thanks
> >
> > Matt
> >
> > [1] https://github.com/apache/nifi/pull/8053
> >
> > On Mon, Nov 27, 2023 at 1:24 PM Dan S  wrote:
> >
> > > I pulled from the latest code and I cannot build in order to submit a
> > PR. I
> > > am getting the following
> > >
> > > [ERROR] Failed to execute goal
> > > com.github.eirslett:frontend-maven-plugin:1.14.2:npm (npm-install) on
> > > project nifi-web-frontend: Failed to run task: 'npm run ci' failed.
> > > org.apache.commons.exec.ExecuteException: Process exited with an
> error: 1
> > > (Exit value: 1) -> [Help 1]
> > >
> > > Does anyone have any suggestions how this can be fixed?
> > >
> >
>

Re: Cannot build in order to submit PR

[Matt Gilman]

Hi Dan,

We did land an effort that introduces the beginnings of a new UI [1]. I
never ran into this and the GitHub CI for the PR ran successfully but
someone else had an issue earlier today too. The actual error should be
reported above the summary at the bottom of your build output. Can you
please check for those details and see if re-running the build helps? We'd
like to run down if there are any issues here so others don't run into them
too.

Thanks

Matt

[1] https://github.com/apache/nifi/pull/8053

On Mon, Nov 27, 2023 at 1:24 PM Dan S  wrote:

> I pulled from the latest code and I cannot build in order to submit a PR. I
> am getting the following
>
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.14.2:npm (npm-install) on
> project nifi-web-frontend: Failed to run task: 'npm run ci' failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1) -> [Help 1]
>
> Does anyone have any suggestions how this can be fixed?
>

Re: [discuss] NiFi 2 and Node.js version

[Matt Gilman]

Chris,

Thanks for raising this. Node.js (and npm) are used at build time to
package the front-end applications. Bumping those versions should be
doable. However, the front end still uses a lot of legacy and now
unsupported dependencies and also requires updating. This aspect is a
much larger effort. There is a JIRA [1] filed for migrating the front end
to current versions of these dependencies. That work is underway and things
are progressing nicely. The JIRA also lays out a high-level plan for
introducing this change without impacting the existing UI until it's fully
ready.

[1] https://issues.apache.org/jira/browse/NIFI-11481

On Tue, Oct 10, 2023 at 3:16 PM Chris Sampson
 wrote:

> The main focus of NiFi 2.x has so far been to upgrade Java to JDK 21 and
> remove deprecated/unmaintained code and artefacts.
>
> The NiFi & NifI Registry UIs are currently using Node.js v16, which is an
> LTS release, but is imminently due to be end of life [1]. Node.js v18 has
> been the current LTS release since October 2022, although v20 is about to
> take over that spot.
>
> Should the NiFi 2.x milestone include an upgrade of the UI frameworks to
> (at least) Node.js v20, or v18 if there are compatibility issues with
> dependencies used?
>
> If this is already on somebody’s roadmap, then great, but I just noticed
> this in the pom.xml files and thought it was worth raising.
>
>
> [1]: https://nodejs.dev/en/about/releases/
>
> Cheers,
>
> ---
> Chris Sampson
> IT Consultant
> chris.samp...@naimuri.com
>
>
>

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

[Matt Gilman]

+1 (binding)

Ran through release helper and verified basic functionality. Looks good.
Thanks for RMing David!

Matt

On Tue, Aug 22, 2023 at 2:15 PM Marton Szasz  wrote:

> +1 (binding)
> Verified the usual: README, NOTICE, LICENSE, commit id, contents,
> hashes, signature, build
> Manual tested NiFi with a simple flow.
>
> Apache Maven 3.6.3
> Maven home: /usr/share/maven
> Java version: 17.0.8, vendor: Private Build, runtime:
> /usr/lib/jvm/java-17-openjdk-amd64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "6.2.0-26-generic", arch: "amd64", family:
> "unix"
>
> Thanks,
> Marton
>
> On Tue, Aug 22, 2023 at 8:14 PM Nandor Soma Abonyi
>  wrote:
> >
> > +1 (binding)
> >
> > Connected to NiFi registry, imported and committed some flows.
> >
> > Verified for regression:
> > - Azure ADLS related flows
> >
> > Ran a flow to verify the fix for NIFI-11971
> >
> > Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
> > Maven home: /usr/share/maven
> > Java version: 1.8.0_362, vendor: Temurin, runtime: /opt/java/openjdk/jre
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "6.4.8-orbstack-00059-g106c60a3471f", arch:
> "aarch64", family: "unix"
> >
> > Thanks for the quick turnaround all!
> >
> > Regards,
> > Soma
> >
> > > On 2023. Aug 21., at 22:16, David Handermann <
> exceptionfact...@apache.org> wrote:
> > >
> > > Team,
> > >
> > > NOTE: This is a shortened vote window given the narrow scope of
> changes.
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi 1.23.2.
> > >
> > > Please review the following guide for how to verify a release
> candidate build:
> > >
> > >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > >
> > > The source being voted on the and the convenience binaries are
> > > available on the Apache Distribution Repository:
> > >
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.23.2
> > >
> > > The build artifacts are available on the Apache Nexus Repository:
> > >
> > > https://repository.apache.org/content/repositories/orgapachenifi-1235
> > >
> > > Git Tag: nifi-1.23.2-RC1
> > > Git Commit ID: dec043e590f26ba2f3594f4f297dcd2b7e565ab7
> > > GitHub Commit Link:
> > >
> https://github.com/apache/nifi/commit/dec043e590f26ba2f3594f4f297dcd2b7e565ab7
> > >
> > > Checksums of nifi-1.23.2-source-release.zip
> > >
> > > SHA256:
> cfaa374c383a316de6d9230a0786ebe7dd97c03f8903b36365faa27bf6424fac
> > > SHA512:
> a63fa624532aa3f1769013d67499caf48b9771bc3515ffca4daba2dd379722c3b25bea4519b56bc647d4e05db122e7a41519a52a703a0179b431fa881dadb4cf
> > >
> > > Release artifacts are signed with the following key:
> > >
> > > https://people.apache.org/keys/committer/exceptionfactory.asc
> > >
> > > KEYS file is available on the Apache Distribution Repository:
> > >
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > Issues resolved in this version: 1
> > >
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12353568
> > >
> > > Release note highlights can be found on the project wiki:
> > >
> > >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.23.2
> > >
> > > The vote will be open for 24 hours.
> > >
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> > > Then please vote:
> > >
> > > [] +1 Release this package as nifi-1.23.2
> > > [] +0 no opinion
> > > [] -1 Do not release this package because...
> >
>

Re: Refreshing HTML displayed for View usage

[Matt Gilman]

Russell,

Thanks for the response. The suggestion to open a new tab was for the
generated documentation, not the NiFi canvas itself. The generated
documentation is shown in an iframe which will offer you the menu item in
the context menu for opening in a new tab. IIRC correctly, the path to the
generated documentation contains the version of the component. For folks
simply using a released version of NiFi this works great since versions
will differ and any browser caching will only optimize page loading for the
user. If you're a developer, however, you're likely making changes to your
component and the version is not changing (x.y.z-SNAPSHOT). This is where
the browser cache could result in the behavior your seeing.

Matt

On Thu, Aug 17, 2023 at 3:21 PM Russell Bateman 
wrote:

> Thanks, Matt,
>
> (Since I use Chrome 99% of the time, I'm using Chrome here.)
>
> Clicking on the reload control next to the address bar, while holding
> down Shift, reloads the canvas, but the NiFi Documentation page
> disappears and I have to reload it using the View usage context menu of
> my processor. Once reloaded, nothing has changed.
>
> This is also the behavior of the Configure Processor dialog. As I reload
> View usage, ...
>
> In Chrome, there's no effective content-menu option to right-click in
> the page contents and open in a new tab. I can...
>
> Back
> Forward
> Reload
> ---
> Save As...
> Print
> Cast
> Search images with Google
> -
> Send to your devices
> Create QR code for this page
> 
> Translate
> -
> View page source
> View frame source
> Reload frame
> Inspect
>
>
> If I right-click the current tab itself, I'm able to choose to
> Duplicate., but that doesn't seem to lead to anything more helpful.
>
> By the way, I'm doing this using NiFi 1.23.0. I have also verified the
> date of my NAR to ensure that I'm not repeatedly working using a NAR
> with old content. Also, the version displayed for the custom processor
> is that of the various /pom.xml/ files I'm building with.
>
> I usually develop on the latest NiFi version. However, my company has
> NARs that won't load beginning 1.14.0. I just brought up 1.13.2, what
> most of our customers run, and tried my latest NAR which *does* display
> my changes.Same with 1.1.2, which represents the oldest platform
> executing at any custom site. Exceptionally, I set up 1.19.1 where it
> *also works*.
>
> This is unexpected; maybe it does point, as unlikely as it seems, to
> something changed in 1.23.0 (instead of being caused by anything between
> the dossier of my chair and the space bar of my keyboard as I have been
> expecting to learn. ;-)  )
>
> It could still be me and I'm just not seeing the obvious yet.
>
>
> On 8/17/23 12:44, Matt Gilman wrote:
> > Russell,
> >
> > Assuming this is a browser cache issue, can you try right-clicking
> anywhere
> > in the page contents of the generated documentation and open it in a new
> > tab. Once that is open, can you try doing a hard refresh by holding Shift
> > while clicking Reload next to the address bar? This should clear the
> cache
> > and fetch the updated generated documentation. At this point, you should
> be
> > able to close that tab and retry from the NiFi UI.
> >
> > Let us know if this doesn't help and we can see if something isn't
> getting
> > generated and updated correctly.
> >
> > Matt
> >
> > On Thu, Aug 17, 2023 at 2:38 PM Russell Bateman
> > wrote:
> >
> >> Seems like a really stupid user/browser question, but I cannot seem to
> >> get changes I've made to properties, relationships, attributes read or
> >> written, etc. *for custom processors*. Also, from the Properties tab in
> >> Configuring Processor, the cartoon blurbs obtained by hovering over (?)
> >> aren't updated either.
> >>
> >> This is despite that changes I make to my /additionalDetails.html/ files
> >> come through with no problem.
> >>
> >> I have tried Chrome, Opera, Brave and Firefox. All [mis]behave
> identically.
> >>
> >> I have tried killing the browser running the NiFi UI, stopping also the
> >> NiFi instance, relaunching NiFi, quickly asking the browser to display
> >> the canvas, then holding down the Ctrl key as I click Reload.
> >>
> >> In past times, I have observed that eventually the changes are
> >> recognized and displayed, so this is not permanent, however, it's very
> >> annoying especially when I'm polishing my processor documentation
> >> wording in the class that extends AbstractProcessor. All the while, as I
> >> say, the processor's corresponding /additionalDetails.html/ displays
> >> changes I make to it in a timely and accurate fashion.
> >>
> >> Suggestions?
>

Re: Refreshing HTML displayed for View usage

[Matt Gilman]

Russell,

Assuming this is a browser cache issue, can you try right-clicking anywhere
in the page contents of the generated documentation and open it in a new
tab. Once that is open, can you try doing a hard refresh by holding Shift
while clicking Reload next to the address bar? This should clear the cache
and fetch the updated generated documentation. At this point, you should be
able to close that tab and retry from the NiFi UI.

Let us know if this doesn't help and we can see if something isn't getting
generated and updated correctly.

Matt

On Thu, Aug 17, 2023 at 2:38 PM Russell Bateman 
wrote:

> Seems like a really stupid user/browser question, but I cannot seem to
> get changes I've made to properties, relationships, attributes read or
> written, etc. *for custom processors*. Also, from the Properties tab in
> Configuring Processor, the cartoon blurbs obtained by hovering over (?)
> aren't updated either.
>
> This is despite that changes I make to my /additionalDetails.html/ files
> come through with no problem.
>
> I have tried Chrome, Opera, Brave and Firefox. All [mis]behave identically.
>
> I have tried killing the browser running the NiFi UI, stopping also the
> NiFi instance, relaunching NiFi, quickly asking the browser to display
> the canvas, then holding down the Ctrl key as I click Reload.
>
> In past times, I have observed that eventually the changes are
> recognized and displayed, so this is not permanent, however, it's very
> annoying especially when I'm polishing my processor documentation
> wording in the class that extends AbstractProcessor. All the while, as I
> say, the processor's corresponding /additionalDetails.html/ displays
> changes I make to it in a timely and accurate fashion.
>
> Suggestions?

Re: assistance with install process

[Matt Gilman]

Hi,

The maven process should download and install node and npm within the
target directory. You shouldn't need to install them on your system
manually. The actual npm commands once installed are also executed from the
target directory of that module. This is why the file package.json does not
exist in the source root or directly in that module as well. Would it you
possible for you to share more output from the failed maven command? If you
scroll further back it may have additional details regarding the issue.

Thanks

On Fri, Apr 14, 2023 at 11:11 AM Mark Woodcock 
wrote:

> Howdy,
>
> (N.B. I'm a VisProfessor at the USNA; I would like to teach the mids to use
> NiFi as part of a new "big data" course we are offering this coming fall.)
>
> I'm just trying to get the software installed (latest and greatest;
> unzipped and then "mvn clean install").
> (N.B. I did have to do some supporting installs to get "npm" to work, but
> those seemed to go cleanly).
>
> It keeps jamming here:
>
> [ERROR] Failed to execute goal
> com.github.eirslett:frontend-maven-plugin:1.12.1:npm (npm install) on
> project nifi-web-ui: Failed to run task: 'npm run ci' failed.
> org.apache.commons.exec.ExecuteException: Process exited with an error: 1
> (Exit value: 1) -> [Help 1]
>
> when I try to run "npm run ci" on its own (in either the root or that
> nifi-web-ui dir), I get:
>
> npm ERR! enoent ENOENT: no such file or directory, open
> '/home/scs/woodcock/nifi-1.21.0/package.json'
>
> which, you know, fair enough; it ain't there.  but I have no idea what
> should be there, or how it was supposed to get there.
> (there are tons of package.json files about, just not in either of those
> locations).
>
> thx much,
>
> mew
>

Re: [VOTE] Adopt NiFi 2.0 Proposed Release Goals

[Matt Gilman]

+1 (binding)

On Mon, Dec 12, 2022 at 12:02 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Team,
>
> Following positive feedback on NiFi 2.0 Proposed Release Goals [1] on the
> recent discussion thread [2], I am calling this vote to adopt the following
> as Release Goals for NiFi 2.0:
>
> 1. Remove Java 8 support and require Java 11
> 2. Remove deprecated components
> 3. Remove deprecated component properties
> 4. Remove components integrating with unmaintained services
> 5. Remove compatibility classes and methods
> 6. Remove flow.xml.gz in favor of flow.json.gz
> 7. Remove duplicative features
> 8. Upgrade internal Java API references
> 9. Reorganize standard components
> 10. Implement migration tools for upgrading flows
>
> A positive vote indicates agreement on these goals and the initiation of
> the following actions:
>
> 1. Rename NiFi 2.0 Proposed Release Goals to NiFi 2.0 Release Goals
> 2. Create version 1 branch in Git for subsequent support releases on the
> version 1 series
> 3. Update the current main branch in Git to version 2.0.0-SNAPSHOT
>
> The vote will be open for 72 hours and follow standard procedures for
> release votes.
>
> Please review the linked goals and discussions for background.
>
> [ ] +1 Adopt NiFi 2.0 Release Goals
> [ ] +0 No opinion
> [ ] -1 Do not adopt NiFi 2.0 Release Goals for the following reasons...
>
> [1]
>
> https://cwiki.apache.org/confluence/display/NIFI/NiFi+2.0+Proposed+Release+Goals
> [2] https://lists.apache.org/thread/xo77p9t3xg4k70356xrqbdg4m9sg7sf8
>

Re: Controller Service which can not validate has spinning Validating and does not display Invalid until refreshed

[Matt Gilman]

Hi Dan,

Thanks for reaching out. After saving the configuration, the UI does reload
the component that was modified. However, as you noted when the validating
is lengthy the Status may still be Validating. This listing and other
listings throughout the application do not automatically refresh like the
canvas does. As you described, the contents of the listing required you to
manually refresh with the button at the bottom of the table. Free feel to
file a JIRA regarding this issue. While supporting automatically refreshing
every listing in the application is a larger effort, we could consider
continuing to reload in this specific scenario.

Thanks

Matt

On Fri, Oct 7, 2022 at 3:53 PM Dan S  wrote:

> I am working on a Avro schema directory registry as detailed in NIFI-10428
> .
> After configuring this service, validation fails as I see an icon with an
> error log message but the state column has "Validating" with a spinning
> icon. If I use the refresh icon, then the state turns to "Invalid". How can
> I avoid this hanging of validation in the UI?
>

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

[Matt Gilman]

+1 (binding)

Ran through helper and focused verification on new UI features introduced
in this release. Thanks for RMing Joe!

Matt

On Wed, Mar 23, 2022 at 2:28 PM Tamás Pálfy 
wrote:

> +1 non-binding
>
> - NIFI-9065  Verified
> InvokeHTTP and StandardOauth2AccessTokenProvider integration
> - NIFI-8676  Verified
> Tracking
> Entities Listing Strategy in ListS3
> - NIFI-9334  Verified
> upsert in PutMongoRecord
>
> On Wed, Mar 23, 2022 at 5:02 PM Marton Szasz  wrote:
>
> > +1 (binding)
> >
> > Followed the release helper guide.
> > Built on Gentoo, OpenJDK 8, and Ubuntu 20.04 OpenJDK 8 and OpenJDK 17.
> > Smoke tested the binary with ListenHTTP -> LogAttribute.
> >
> > On Wed, 23 Mar 2022 at 14:47, Joe Gresock  wrote:
> > >
> > > +1 non-binding
> > >
> > > - Verified signatures and hashes
> > > - Built on Java 8, Mac OS 12
> > > - Tested upgrading a 3-node NiFi 1.15.0 cluster to the release
> candidate
> > > - Verified load balancing on a queue, as well as several recent bugs
> > >
> > > Joe Gresock
> > >
> > > On Wed, Mar 23, 2022 at 9:57 AM gre...@yahoo.com.INVALID
> > >  wrote:
> > >
> > > > +1
> > > >
> > > > - Verified signatures and hashes of [
> > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.0/] binaries
> > > > - Build of source successful (macOS 12 / Azul Java 17)
> > > > - Application startup successful (set-single-user-credentials, three
> > node
> > > > dev cluster)
> > > > - Verified successful flow of data using known good flows (SFTP,
> > > > QueryDatabase/PutDatabase, PutSlack)
> > > > - Sanity check of cluster disconnect / offload / connect operations
> > > > - JIRA NIFI-9824 created for minor logging issue
> > > >
> > > > Thanks Joe!
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Monday, March 21, 2022, 05:41:58 PM EDT, Joe Witt <
> > joew...@apache.org>
> > > > wrote:
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > Hello,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > > 1.16.0.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > >
> https://repository.apache.org/content/repositories/orgapachenifi-1198
> > > >
> > > > The source being voted upon and the convenience binaries can be found
> > at:
> > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.0/
> > > >
> > > > A helpful reminder on how the release candidate verification process
> > works:
> > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> > > >
> > > > The Git tag is nifi-1.16.0-RC3
> > > > The Git commit ID is b019a9191f1c83bc7f547dc02c1b679b8936acee
> > > >
> > > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=b019a9191f1c83bc7f547dc02c1b679b8936acee
> > > >
> > > > Checksums of nifi-1.16.0-source-release.zip:
> > > > SHA256:
> > 2f16cb94df404d1bcc9c32835ba98da8940005a5d7ea5504c155ee42021a221e
> > > > SHA512:
> > > >
> > > >
> >
> cbd95f15cec5ffe506fef204526267b18b77d7266f6dc3e1bbc3c7600aac12e119977f7d8cf93dbbbc86fbb0739ba88aaa11a5381d29a463ec9a0c9a18f4e9e6
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/joewitt.asc
> > > >
> > > > KEYS file available here:
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > > 401 issues were closed/resolved for this release:
> > > >
> > > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12350741
> > > >
> > > > Release note highlights can be found here:
> > > >
> > > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.0
> > > >
> > > > The vote will be open for 72 hours.
> > > > Please download the release candidate and evaluate the necessary
> items
> > > > including checking hashes, signatures, build from source, and test.
> > Then
> > > > please vote:
> > > >
> > > > [ ] +1 Release this package as nifi-1.16.0
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> >
>

Re: nifi.apache.org website

[Matt Gilman]

Thanks Jon. The invite link for Slack is at the bottom of this page [1].

[1] https://nifi.apache.org/mailing_lists.html

On Wed, Mar 16, 2022 at 4:46 PM Jonathan Conti-Vock <
jonathan.contiv...@gmail.com> wrote:

> Thanks for the update Steven. Correct me if I'm wrong, but I'll need
> someone to invite me as a guest to follow along in the slack channel,
> correct? I would be happy to and interested in lending my UI/UX experience
> to this conversation.
>
> Cheers,
>
> Jon
>
> On Wed, Mar 16, 2022 at 3:39 PM Steven Matison 
> wrote:
>
> > Just a quick update on this thread.  Progress has been made and we have
> an
> > initial hugo framework able to run the current site.
> >
> > Please join us in follow on conversation in #apachenifiwebsite on slack!
> >
> >
> >
> > On Fri, Mar 11, 2022 at 8:25 AM Joe Witt  wrote:
> >
> > > done.  and added you
> > >
> > > On Fri, Mar 11, 2022 at 6:17 AM Steven Matison <
> steven.mati...@gmail.com
> > >
> > > wrote:
> > >
> > > > So glad there is such an interest in this.
> > > >
> > > > Can we move discussion into a slack channel dedicated to this topic?
> > > >
> > > > On Wed, Mar 9, 2022 at 2:47 PM Steven Matison <
> > steven.mati...@gmail.com>
> > > > wrote:
> > > >
> > > > > Sounds awesome, gimme some time to go through everything you guys
> > have
> > > > > shared.
> > > > >
> > > > >
> > > > >
> > > > > On Wed, Mar 9, 2022 at 2:28 PM Andrew Lim <
> > andrewlim.apa...@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> Hi Steven,
> > > > >>
> > > > >> Excited by your interest in this! A Jira was created to migrate
> the
> > > NiFi
> > > > >> website to ASF git build/deploy [1]. I’ve been meaning to work on
> it
> > > but
> > > > >> haven’t had the cycles.
> > > > >>
> > > > >> In my research on static-site generators, Hugo [2] came up as a
> very
> > > > >> strong candidate especially due to its speed. There are 10 Apache
> > > > websites
> > > > >> that currently use Hugo [3]. Apache Jena is one of them and that
> > team
> > > > >> documented their migration steps on their wiki [4].
> > > > >>
> > > > >> Perhaps you could do some research and share your findings. If we
> > can
> > > > get
> > > > >> a working version of the current NiFi website in a chosen
> generator,
> > > we
> > > > can
> > > > >> get a Discuss thread going in the community similar to what Apache
> > > Jena
> > > > did
> > > > >> [5].
> > > > >>
> > > > >> I would love to help with the migration as well as a refresh of
> the
> > > > site!
> > > > >>
> > > > >> -Drew
> > > > >>
> > > > >>
> > > > >> [1] https://issues.apache.org/jira/browse/NIFI-6848 <
> > > > >> https://issues.apache.org/jira/browse/NIFI-6848>
> > > > >> [2] https://gohugo.io/ 
> > > > >> [3]
> > > > >>
> > >
> https://github.com/search?q=topic%3Ahugo+org%3Aapache&type=Repositories
> > > > <
> > > > >>
> https://github.com/search?q=topic:hugo+org:apache&type=Repositories
> > >
> > > > >> [4]
> > > > >>
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
> > > > >> <
> > > > >>
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS
> > > > >> >
> > > > >> [5]
> > https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr
> > > <
> > > > >> https://lists.apache.org/thread/tt4mm3phpkjxf7kc5hp3t006sob7ksqr>
> > > > >>
> > > > >>
> > > > >> > On Mar 9, 2022, at 1:59 PM, David Handermann <
> > > > >> exceptionfact...@apache.org> wrote:
> > > > >> >
> > > > >> > Hi Steven,
> > > > >> >
> > > > >> > Thanks for your interest! This would also be a great opportunity
> > to
> > > > >> > streamline the HTML generation approach to use something like
> Hugo
> > > or
> > > > >> > similar static-site generation system.
> > > > >> >
> > > > >> > Regards,
> > > > >> > David Handermann
> > > > >> >
> > > > >> > On Wed, Mar 9, 2022 at 12:44 PM Joe Witt 
> > > wrote:
> > > > >> >
> > > > >> >> Steven
> > > > >> >>
> > > > >> >> To say this is super welcome is an understatement.  We
> definitely
> > > > need
> > > > >> the
> > > > >> >> facelift you mention and we need to get off the old website
> > > mechanism
> > > > >> and
> > > > >> >> onto the newer one the ASF wants projects using.  This would be
> > > > >> awesome!
> > > > >> >>
> > > > >> >> Thanks!
> > > > >> >>
> > > > >> >>
> > > > >> >> On Wed, Mar 9, 2022 at 11:40 AM Steven Matison <
> > > > >> steven.mati...@gmail.com>
> > > > >> >> wrote:
> > > > >> >>
> > > > >> >>> Hey Dev Team,
> > > > >> >>>
> > > > >> >>>  Is there any way I could assist with modernizing the
> > > > >> >> nifi.apache.org
> > > > >> >>> website?
> > > > >> >>>
> > > > >> >>> Its 2022 and I think a facelift is in order...  I have a ton
> of
> > > > >> >> experience
> > > > >> >>> with web-dev and super passionate about NiFi.  This would be
> > > > >> something I
> > > > >> >>> would love to be a part of.
> > > > >> >>>
> > > > >> >>> Thanks,
> > > > >> >>>
> > > > >> >>> Steven
> > > >

Re: [VOTE] Release Apache NiFi Flow Design System 0.3.0 RC2

[Matt Gilman]

+1 (binding) Release this package as nifi-fds-0.3.0

Ran through release helper. Looks good. Thanks for RMing Scott!

Matt

On Tue, Jan 25, 2022 at 4:41 PM Scott Aslan  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> Flow Design System nifi-fds-0.3.0.
>
> The source zip, including signatures, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.3.0
>
> The Git tag is nifi-0.3.0-RC2
> The Git commit ID is a17b6712154f1b7bf36a04cfe728b61640843807
>
> https://gitbox.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=a17b6712154f1b7bf36a04cfe728b61640843807
>
> Checksums of nifi-fds-0.3.0-source-release.zip:
> SHA1: 92e473c2c0da9f031c47724ade9808f7572dd6bd
> SHA256: 200c8f6a2a7fcdfa5a65c73dfef887c0173a9bf10d73ee7ac0160a614e9202ff
> SHA512:
>
> 74b93eb29a5e0bfefd25de288f387308307de63cf159f0c447565615a32b041fe5af20a326528a5dc8e99bf3adc8bbdc157cfa10090d51b30f958bb6253201b9
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/scottyaslan.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 17 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345959
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.3.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.  Then
> please vote:
>
> [ ] +1 Release this package as nifi-fds-0.3.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: Jira contributor access

[Matt Gilman]

Marshall,

You've been assigned contributor in Apache NiFi JIRA.

Thanks

Matt

On Fri, Jan 21, 2022 at 2:21 PM Marshall Newberry 
wrote:

> Requesting Jira contributor access for user dmnewber.
>

Re: NiFi HTML modification issue

[Matt Gilman]

Jamal,

In order to modify the markup that is returned to the browser, you'll need
to update the front-end resources in the NiFi sources and rebuild a new
assembly. The files you reference in nifi-current/work directory are in a
working directory that may be (re)generated at runtime. By updating the
resources and building a new assembly, your changes will be included in the
basis for the generated markup. If you need to update something on every
page in the NiFi UI, you'd need to update each file here [1].

Hope this helps!

Matt

[1]
https://github.com/apache/nifi/tree/main/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-ui/src/main/webapp/WEB-INF/pages

On Wed, Jan 5, 2022 at 1:32 PM Jamal Wills 
wrote:

> I'm trying to modify a NiFi instance (NiagaraFiles Community 4.14.0 with
> Apache Nifi 0.7.1.c) to instrument the user interface using AppDynamics. It
> requires that I insert a code snippet  for the JavaScript end user
> monitoring agent.  I have found that it has .jsp files where I would expect
> to insert the code, but it looks like the code gets replaced each time I
> make a modification.
>
>
> https://docs.appdynamics.com/21.4/en/end-user-monitoring/browser-monitoring/browser-real-user-monitoring/inject-the-javascript-agent/manual-injection-of-the-javascript-agent
> Manual Injection of the JavaScript Agent<
> https://docs.appdynamics.com/21.4/en/end-user-monitoring/browser-monitoring/browser-real-user-monitoring/inject-the-javascript-agent/manual-injection-of-the-javascript-agent
> >
> This page describes how to instrument a browser application by manually
> injecting the JavaScript Agent. To configure the JavaScript Agent before
> injection, see Configure the JavaScript Agent.. Manually Inject the
> JavaScript Agent
> docs.appdynamics.com
> The files, I found are under the nifi-current/work directory.  I'm
> assuming the files are replaced by the files in the lib and lib_community
> directories which appear to be unfamiliar archive files. Would the
> modifications have to be made to those files?
>
> Thanks,
> Jamal Wills
>
>

Re: How to run nifi in a development environment

[Matt Gilman]

Hi Roy,

By default, the maven build will minify and aggregate all the front-end
resources. There is a profile that you can (de)activate to instead bundle
the resources as they are in the source. This should look something like:

mvn clean install -P-minify-and-compress

When running the resulting build you should be able to inspect things with
DevTools and set breakpoints in the debugger. Subsequent iterations can be
made faster by only building the necessary modules needed to bundle a new
front-end. Specifically, that is nifi-web-ui (don't forget to deactivate
minify-and-compress) and nifi-server-nar. The resulting NAR from the target
directory in nifi-server-nar will need to be copied to the lib directory of
your previously built assembly.

Unfortunately, there is no way to run just the front-end in a dev server
decoupled from the backed. The NiFi front-end sources are in JSPs which
generate markup server side.

Hope this helps.

Matt

On Tue, Dec 21, 2021 at 10:24 PM Roy Huang  wrote:

> Hi everyone
>
> I want to modify some css style in nifi, but I don't know how to run it in
> a dev environment, can you help me with that? I'm a front-end developer and
> don't know about java maven.
>

Re: [VOTE] Release Apache NiFi 1.15.2

[Matt Gilman]

+1 (binding) Release this package as nifi-1.15.2

Ran through the release helper. Looks great. Thanks for RMing Joe!

Matt

On Tue, Dec 21, 2021 at 5:52 PM Joe Witt  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.15.2.
>
> This vote is purely bug fix and security focused. This is a
> continuation of our efforts to promptly and thoroughly respond to
> log4shell and related concerns.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1193
>
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.2/
>
> A helpful reminder on how the release candidate verification process works:
>
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>
> The Git tag is nifi-1.15.2-RC1
> The Git commit ID is 1ea460b8556b07057366abb74a5552ace8946e87
>
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=1ea460b8556b07057366abb74a5552ace8946e87
>
> Checksums of nifi-1.15.2-source-release.zip:
> SHA256: 29fcc35c81de80e0fe3f59044e6fbf21bcf523e656aa64914e7546e1d7705e6b
> SHA512:
> cabd1f1ad4942a61df0400488d35521202598c217ad8da97dc2d5abe21136604d1f1bb3de9ceb63bb441943de2e29e3515f5cf63607080094e1418d79eb5216b
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 8 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12351132
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.2
>
> Given the nature of the vote and its limited scope
> the vote will be open for 24 hours or until we have sufficient
> votes (instead of the normal 72 hours).
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> Then please vote:
>
> [ ] +1 Release this package as nifi-1.15.2
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

[ANNOUNCE] New Apache NiFi Committer Margot Tien

[Matt Gilman]

Apache NiFi community,

On behalf of the Apache NiFi PMC, I am very pleased to announce that Margot
has accepted the PMC's invitation to become a committer on the Apache NiFi
project. We greatly appreciate all of Margot's hard work and generous
contributions to the project. We look forward to continued involvement in
the project.

Margot has been contributing to NiFi and NiFi Registry for years. Her
contributions have covered both back-end and front-end improvements in both
projects in addition to release verification and thoughtful PR reviews.

Welcome and congratulations!

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

[Matt Gilman]

+1 (binding)

Ran through the release helper. Looks great.

Thanks for RMing Joe!

On Tue, Dec 14, 2021 at 10:35 PM Joe Witt  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi 1.15.1.
>
> This vote, unlike most, is purely stability and security focused.
> This vote is rooted
> in a prompt response to the 'log4shell' vulnerability and related
> logging announcements.
> It also includes other easy to incorporate bugs and improvements.  It
> should be easy to
> upgrade from any 1.15 install to this and just as easy as it was to go
> from pre 1.15 to
> this 1.15.1.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1192
>
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.15.1/
>
> A helpful reminder on how the release candidate verification process works:
>
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>
> The Git tag is nifi-1.15.1-RC1
> The Git commit ID is 2a756372fc7097ece6258c2af47b9a5f26384b02
>
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=2a756372fc7097ece6258c2af47b9a5f26384b02
>
> Checksums of nifi-1.15.1-source-release.zip:
> SHA256: 83d06011f0d2608d2d9cf951deae04d7b0921f2a7c8b1052ca9d058cf46b7d52
> SHA512:
> 009161e81e207a16060d9efd37e9b9abd1c1d5b5d57024a2b4c0d0ea17050f65b3a025632718161cba41948fe51d93aed65a4daba2542fce4da51d0184872039
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 45 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12351055
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.15.1
>
> Given the nature of the vote being about a prompt release to remove
> vulnerable
> logging related libraries the vote will be open for 24 hours (instead
> of the normal 72 hours).
>
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> Then please vote:
>
> [ ] +1 Release this package as nifi-1.15.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

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

[Matt Gilman]

+1 (binding)

Ran through the release helper. Looked great! Thanks for RMing Bryan!

Matt

On Thu, Dec 2, 2021 at 11:28 AM Matt Burgess  wrote:

> +1 (binding), ran through release helper and verified NARs were loaded
> successfully into a NiFi instance.  Thanks for RM'ing Bryan!
>
> On Tue, Nov 30, 2021 at 3:56 PM Bryan Bende  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi NAR Maven Plugin 1.3.3.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1188
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-1.3.3/
> >
> > A helpful reminder on how the release candidate verification process
> works:
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> >
> > The Git tag is nifi-nar-maven-plugin-1.3.3-RC1
> > The Git commit ID is 99f1ff7184e00cecc4763b7bcbdf0d12dfeffef2
> >
> https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=99f1ff7184e00cecc4763b7bcbdf0d12dfeffef2
> >
> > Checksums of nifi-nar-maven-plugin-1.3.3-source-release.zip:
> > SHA256: 36d6579dfdbc4e1450a13457196ff399dbd344624348a62ee5e247cd5962dc77
> > SHA512:
> 0e90100d90e9dd142283aab729957e12cc6abbfdf2f86447f488bcbe5890d55564c19a0efc473307744f813bcdac2636b027ad4e5beebf1ce1ed6ee44deaccbe
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/bbende.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 1 issue was closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12348815
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion1.3.3
> >
> > The vote will be open for 72 hours. Please download the release
> > candidate and evaluate the necessary items including checking hashes,
> > signatures, build from source, and test. Then please vote:
> >
> > [ ] +1 Release this package as nifi-nar-maven-plugin-1.3.3
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>

Re: NiFi UI Slowness

[Matt Gilman]

Aswin K,

Most often UI slowness is due to lengthy web requests. You should be able
to confirm this by inspecting the Network tab of your browser's Dev tools.
If this is the case, which calls are slow? What version of NiFi are you
using? How is your flow structured? Are all processors in the root Process
Group or have you structured your flow hierarchically?

If the web requests aren't taking too long, what browser are you using? If
you are running Chrome 92 there was a regression [1] introduced that
affects SVG heavy web applications like NiFi. If you're using this browser
I would suggest trying another browser like Firefox.

Matt

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=1235045

On Tue, Aug 31, 2021 at 8:27 AM Aswin K  wrote:

> Hi Team,
>
> I am using a 3node NiFi cluster. Total 452 processors are using both
> standard and custom processors.
> Now i am going to add one more processors, I am bit scary while adding the
> addtion processors because of system capacity. Also while i can see the UI
> is bit slow even if i open any of the processor
>
> Would you let me know what sort of measurement i need to figure out
> especially this cases.
>

Re: [VOTE] Release Apache NiFi 1.13.2

[Matt Gilman]

Hi Mark,

Thanks for reporting this finding. This error message happens when either a
request to fetch the rules or the evaluation criteria fail. I would expect
there to be more details in your user log and in the response text if you
check DevTools for these web requests. I am going to try to replicate the
failure locally but and any additional details you might be able to provide
would be super helpful.

Thanks!

Matt

On Thu, Mar 18, 2021 at 9:35 PM Mark Bean  wrote:

> -1 (non-binding)
>
> In a flow from 1.13.1, UpdateAttribute processor contained rules in the
> Advanced UI. Installed 1.13.2-RC1. Placed 1.13.1 flow.xml.gz into the new
> 1.13.2-RC1 conf/ directory; started NiFi.
>
> The rules in the Advanced UI could not be loaded. UI reports "Unable to
> load the rule list and evalaution criteria." (including the spelling error)
>
> MacOS 11.2.3
> Java 11.0.9
>
> On Thu, Mar 18, 2021 at 1:29 AM Joe Witt  wrote:
>
> > Hello,
> >
> > Please note this has a shorter than normal vote period as this
> > corrects an important regression introduced in 1.13.1 and is purely a
> > focused bug fix release.
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi 1.13.2.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1180
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.13.2/
> >
> > A helpful reminder on how the release candidate verification process
> works:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> >
> > The Git tag is nifi-1.13.2-RC1
> > The Git commit ID is 174938e5e3bfe36951d5607d0d53e78604b0e07b
> >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=174938e5e3bfe36951d5607d0d53e78604b0e07b
> >
> > Checksums of nifi-1.13.2-source-release.zip:
> > SHA256: db18f57b4629367f21f70ec9a332294ec6b6c090a661c974b0fa7a80b09a79be
> > SHA512:
> >
> 279c5701fd7b6d76206f5e79bdf1340d432a8e4834b8e786559095781c77c96a4594e1da040c6b404d1bab615acf5aa9dc60d289e460e6d7261f454f6210c66b
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 5 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12350008
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.13.2
> >
> > The vote will be open for 36 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.
> > Then please vote:
> >
> > [ ] +1 Release this package as nifi-1.13.2
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>

Re: [VOTE] Release Apache NiFi 1.12.0

[Matt Gilman]

+1 (binding) Release this package as nifi-1.12.0

Ran through normal release helper. Verified signatures, checksums, etc.
Full build without issue. Verified basic application functionality.

Thanks for RMing Joe!

On Thu, Aug 13, 2020 at 4:32 PM Joe Witt  wrote:

> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.12.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1165
>
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.12.0/
>
> A helpful reminder on how the release candidate verification process works:
>
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>
> The Git tag is nifi-1.12.0-RC1
> The Git commit ID is 4d940bb151eb8d250b0319318b96d23c4a9819ae
>
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=4d940bb151eb8d250b0319318b96d23c4a9819ae
>
> Checksums of nifi-1.12.0-source-release.zip:
> SHA256: a67ecb34f32cc1f070ebb006b6f05456a2ac663b12f708eadac67754194a6c63
> SHA512:
>
> 2e04235c4d49a76319af7756289ce11554a412bf5f7dcb6dc3915fc931df9f067142820c297e83bc36cb1079fb8384794ef457a20dd00568761eed6621701953
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 335 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12346778
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.12.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
>
> [ ] +1 Release this package as nifi-1.12.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: Urgent: Unable to configure any NiFi processor

[Matt Gilman]

Mohit,

H2 might offer a utility for repairing a corrupted database. In order to get 
NiFi running again, you should be able to move/rename the audit db files and 
restart. NiFi should recreate them on restart. This database is used just to 
store some metadata about users and flow changes. It is not used for managing 
the actual flow state. 

It’s unclear what’s happened to result in a corrupted state. However H2 is a 
library that does get upgraded occasionally. My first thought would be to 
ensure that your always running the latest version of NiFi with the newest 
version of H2 that NiFi’s been upgraded to.

Matt

Sent from my iPhone

> On Jul 11, 2020, at 06:52, Mohit Jain  wrote:
> 
> Hi Team,
> 
> It seems like the nifi-flow-audit.h2.db is corrupted. I'm not able to
> execute the same query on the database directly.
> Anything I can do to fix this?
> And what are the scenarios when this might happen again?
> 
> Regards,
> Mohit
> 
> 
>> On Sat, Jul 11, 2020 at 3:03 PM Mohit Jain  wrote:
>> 
>> Hi Team,
>> 
>> I'm facing a weird issue while trying to configure any NiFi processor:
>> 
>> org.apache.nifi.admin.dao.DataAccessException:
>> org.h2.jdbc.JdbcSQLException: Timeout trying to lock table
>> "CONFIGURE_DETAILS"; SQL statement:
>> SELECT DISTINCT CD.NAME  FROM CONFIGURE_DETAILS CD INNER
>> JOIN ACTION A ON CD.ACTION_ID = A.ID  WHERE A.SOURCE_ID = ?
>> [50200-176]
>> at
>> org.apache.nifi.admin.service.impl.StandardAuditService.getPreviousValues(StandardAuditService.java:102)
>>at
>> org.apache.nifi.web.StandardNiFiServiceFacade.getComponentHistory(StandardNiFiServiceFacade.java:4537)
>>at
>> org.apache.nifi.web.StandardNiFiServiceFacade$$FastClassBySpringCGLIB$$358780e0.invoke()
>> 
>> Complete nifi-user.log is attached in the log.
>> 
>> Any input would be appreciated.
>> 
>> Regards,
>> Mohit
>> 

Re: [VOTE] Release Apache NiFi 1.11.4

[Matt Gilman]

+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 keyPassword is
> empty for nifi.properties, InvokeHTTP, ListenHTTP, and
> HandleHTTPRequest/Response.
>
> Thanks,
> M. Tien
>
> > On Mar 18, 2020, at 10:15 AM, Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.11.4.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1159
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.4/
> >
> > A helpful reminder on how the release candidate verification process
> works:
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> >
> > The Git tag is nifi-1.11.4-RC1
> > The Git commit ID is 4d940bb151eb8d250b0319318b96d23c4a9819ae
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=4d940bb151eb8d250b0319318b96d23c4a9819ae
> >
> > Checksums of nifi-1.11.4-source-release.zip:
> > SHA256: a67ecb34f32cc1f070ebb006b6f05456a2ac663b12f708eadac67754194a6c63
> > SHA512:
> >
> 2e04235c4d49a76319af7756289ce11554a412bf5f7dcb6dc3915fc931df9f067142820c297e83bc36cb1079fb8384794ef457a20dd00568761eed6621701953
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 45 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12347022
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.4
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build
> > from source, and test. Then please vote:
> >
> > [ ] +1 Release this package as nifi-1.11.4
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>
>

Re: [VOTE] Release Apache NiFi 1.11.3

[Matt Gilman]

+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 found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1158
>
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.3/
>
> A helpful reminder on how the release candidate verification process works:
>
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>
> The Git tag is nifi-1.11.3-RC1
> The Git commit ID is 10b509cf5bb88b12b0dd497543291f3c49a9903f
>
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=10b509cf5bb88b12b0dd497543291f3c49a9903f
>
> Checksums of nifi-1.11.3-source-release.zip:
> SHA256: b2544719a8de02892b3436f1e6084b9b6011bf706a183fa2f059a9961634a7bd
> SHA512:
>
> 353671e06dd60e186d2a9a29eb9b7c2d183757f6a0f76801b4ecb5d87aab99e701b9ebde932ee414d4b304afd2bd1d0a0e574906a385cfafc8de36cc47c2d0a3
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 14 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12347022
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.3
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
>
> [ ] +1 Release this package as nifi-1.11.3
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: additionalDetails.html styles

[Matt Gilman]

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-hbase-processors/src/main/resources/docs/org.apache.nifi.hbase.PutHBaseCell/additionalDetails.html

On Thu, Feb 20, 2020 at 12:20 PM Russell Bateman 
wrote:

> I would like to get what I'm offering in /additionalDetails.html/ for my
> custom processor to use the same font style used down the left-hand
> column listing processors (under /NiFi Documentation/). I'm not an idiot
> when it comes to HTML/CSS, however, I have been unable in experimenting
> to see how I can easily grab NiFi's existing style sheets into my HTML.
>
> Has someone done that and can give me an easy, working version of
>
> 
>
> to put into my HTML header?
>
> Profuse thanks!
>

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

[Matt Gilman]

+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, 2020 at 10:15 PM Joe Witt  wrote:
> >
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > 1.11.2.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1157
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.2/
> >
> > A helpful reminder on how the release candidate verification process
> works:
> >
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
> >
> > The Git tag is nifi-1.11.2-RC1
> > The Git commit ID is 6d2ec87c8a46d5d39f3b4683e4ea9dec91138d52
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=6d2ec87c8a46d5d39f3b4683e4ea9dec91138d52
> >
> > Checksums of nifi-1.11.2-source-release.zip:
> > SHA256: 2a030956a7cc9578e616195dd4cf8a853976e17eb040a7b216f844ae2ce9a610
> > SHA512:
> >
> 135101f3f9b37b559e850e79c89bad36d707126fcea559fa4f6846c4cb21c17ab51c119c5005df359a4d3a066c66611b00816c2f7586b24d34f0f418d4b5c527
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 14 issues were closed/resolved for this release:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12346972
> >
> > Release note highlights can be found here:
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.2
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build
> > from source, and test. Then please vote:
> >
> > [ ] +1 Release this package as nifi-1.11.2
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
>

Re: NIFI Flow Design System

[Matt Gilman]

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 component
that FDS offers. When completed that worked would likely land in the next
major version of NiFi. Currently, the canvas in NiFi is implemented
directly in the NiFi codebase and is not designed to be a reusable
component.

Hope this helps clarify things.

On Sat, Feb 15, 2020 at 7:19 AM Glenn Barnard 
wrote:

> Hi, I recently had the pleasure of using NIFI at DXC Technology and was
> wondering if the FDS component was available to use in my own applications.
> I wrote a BPM Workflow engine, but the XML is becoming unmanageable. So,
> I'm looking for a tool I can insert into my web apps to help me in this
> development.
>
> My primary app is Job Manager, which can already perform a series of tasks,
> but Iit needs better flow control that is easy to create, store and test.
>
> Please advise if the Flow Design System would be a good fit for my purposes
> and what I'd have to do to download it.
>
> Thank you so much!
>

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

[Matt Gilman]

+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.11.1.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1156
>
> The source being voted upon and the convenience binaries can be found at:
> https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.1/
>
> A helpful reminder on how the release candidate verification process works:
>
> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate
>
> The Git tag is nifi-1.11.1-RC1
> The Git commit ID is d22858d045fb3e5343a87d362855810963aa8556
>
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=d22858d045fb3e5343a87d362855810963aa8556
>
> Checksums of nifi-1.11.1-source-release.zip:
> SHA256: 41878981689e08c51ed7bb921c46f6328c1e6b6c94460a2382069bd042ab7112
> SHA512:
>
> d309342732196225ffdbac3eaeed3c9b949bcee00509fb6d073618d869c6db56b426f5867849a8ae752d7acc8c6dd18a14cb377655774d86f91d736350eb2041
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 9 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12346906
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.11.1
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
>
> [ ] +1 Release this package as nifi-1.11.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

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

[Matt Gilman]

+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 that can be improved for next time (no
> mention of bootstrap.sh),
> but was able to figure it out by using the README file included in the
> source release.
>
> Hashes & sig all looked good. Was able to build, including the docker
> image. Tests
> all passed. Tested integration with a NiFi cluster with the 0.7.0
> minifi sending flow files over s2s and everything worked as expected.
>
> Overall, seems to be a very solid, polished release. Nice work all!
>
> On Fri, Jan 10, 2020 at 3:35 PM Joe Witt  wrote:
> >
> > +1 (binding)
> >
> > Comments
> > - Notice file copyright year needs to be 2020
> > - I did not enable python support but I get the minifi-python dir anyway
> > and log entry on startup such as
> >Caught Exception ModuleNotFoundError: No module named 'google'
> >
> > Great progress with this release!  Nice work.  Building and running tests
> > was easier than I ever remember.
> >
> > Thanks
> >
> > On Fri, Jan 10, 2020 at 8:27 AM Dániel Bakai 
> > wrote:
> >
> > > +1, non-binding
> > >
> > > Verifications performed:
> > >
> > > SHA256 checksums downloaded: OK
> > > SHA512 checksum of nifi-minifi-cpp-0.7.0-source.tar.gz sent in mail: OK
> > > GPG signatures downloaded: OK
> > > Git tag in email matches sources in
> nifi-minifi-cpp-0.7.0-source.tar.gz: OK
> > >
> > > bootstrap.sh with default options && make && make package && sudo make
> test
> > > ARGS="-j4 --output-on-failure" && run package with a GenerateFlowFile
> ->
> > > LogAttribute flow:
> > >  macOS 10.14.6: TailFileTests sometimes fail, otherwise OK
> > >  ubuntu:bionic docker container: had to install 'tzdata' package for
> > > ExpressionLanguageTest to work, CTailFileChunkTests and
> > > CTailFileDelimitedTests consistently fail when ran in parallel, running
> > > them sequentially works, otherwise OK
> > >  centos:7 docker container: had to install 'zlib-devel' and 'which',
> > > otherwise OK
> > >  debian:stretch docker container: OK
> > >  fedora:29 docker container: had to install 'zlib-devel' and 'which',
> > > otherwise OK
> > >  ubuntu:xenial docker container: had to install 'tzdata' package for
> > > ExpressionLanguageTest to work, otherwise OK
> > >
> > > Run appropriate convenience binary with a GenerateFlowFile ->
> LogAttribute
> > > flow:
> > >  macOS 10.14.6: OK
> > >  ubuntu:bionic docker container: OK
> > >  centos:7 docker container: OK
> > >  debian:stretch docker container: OK
> > >  fedora:29 docker container: OK
> > >  ubuntu:xenial docker container: OK
> > > General note: there is a dynamic libpython dependency in most *nix
> > > convenience binaries, requiring manual installation from the native
> repos,
> > > in the case of CentOS 7 from EPEL.
> > >
> > > win_build_vs.bat build /64 /K /P && ctest -C Release && run package
> with a
> > > GenerateFlowFile -> LogAttribute flow:
> > >  Windows 10: TailFileTests failed, but this is, as far as I know, a
> known
> > > issue, otherwise OK
> > >
> > > Install convenience msi on a completely clean Windows VM and run with a
> > > GenerateFlowFile -> LogAttribute flow both as a service and from
> cmd.exe:
> > >  Windows 7: OK
> > >  Windows 10: OK
> > >
> > >
> > > I think this release brings great improvements over 0.6.0.
> > >
> > > On Fri, 10 Jan 2020 at 02:32, Aldrin Piri 
> wrote:
> > >
> > > > +1, binding
> > > >
> > > > Comments:
> > > > * signature and hashes looked good
> > > > * license and notification looked correct and comprehensive
> > > > * performed build and test successfully on Ubuntu 19.04, CentOS 7,
> and
> > > > MacOS 10.14
> > > > * ran a variety of flows and achieved expected results
> > > > * we should update the helper to have folks make use of the
> bootstrap or
> > > > enumerate the needed dependencies.  the prescribed approach worked
> for me
> > > > as all systems had the requisite tools and dependencies, but others
> may
> > > > experience trying to follow along.
> > > >
> > > > Thanks for acting as RM on this release, Arpad. Lots of great work
> since
> > > > the last release.  Kudos to all the contributors.
> > > >
> > > > On Wed, Jan 8, 2020 at 11:56 AM Arpad Boda  wrote:
> > > >
> > > > > Hello Apache NiFi community,
> > > > >
> > > > > I am pleased to call this vote for the source release of Apache
> NiFi
> > > > MiNiFi
> > > > > C++ 0.7.0
> > > > >
> > > > > The source tar.gz, including signatures, digests, and convenience
> > > > binaries.
> > > > > can be found at:
> > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/0.7.0/
> > > > >
> > > > > The Git tag is minifi-cpp-0.7.0-RC1
> > > > > The Git commit ID is: aa42957a2e227df41510047cece3cd606dc1cb6a
> > > > >
> > > > > Checksum of nifi-minifi-cpp-0.7.0-source.tar.gz:
> > >

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

[Matt Gilman]

+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 used both Java 11 & Java 8 to build.
>
> I did run into a problem compiling with Java 11 and running with Java 8.  I
> don't believe this was a goal of the Java 11 compatibility changes, so
> nothing unexpected about this. But it's possibly worth discussion in
> another thread (which I'll send out).  The convenience binary was compiled
> with Java 8, so no problems with compatibility either way.
>
> On Tue, Oct 29, 2019 at 11:32 AM Joe Witt  wrote:
>
> > Hello,
> >
> > I am pleased to be calling this vote for the source release of Apache
> NiFi
> > nifi-1.10.0.
> >
> > As they say 'third time's a charm'.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1151
> >
> > The source being voted upon and the convenience binaries can be found at:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.10.0/
> >
> > The Git tag is nifi-1.10.0-RC3
> > The Git commit ID is b217ae20ad6a04cac874b2b00d93b7f7514c0b88
> >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=b217ae20ad6a04cac874b2b00d93b7f7514c0b88
> >
> > Checksums of nifi-1.10.0-source-release.zip:
> > SHA256: e9b0a14b3029acd69c6693781b6b6487c14dda12676db8b4a015bce23b1029c1
> > SHA512:
> >
> >
> b07258cbc21d2e529a1aa3098449917e2d059e6b45ffcfcb6df094931cf16caa8970576555164d3f2290cfe064b5780ba1a8bf63dad04d20100ed559a1cfe133
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/joewitt.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 384 issues were closed/resolved for this release:
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12344993
> >
> > Release note highlights can be found here:
> >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.10.0
> >
> > The vote will be open for 72 hours.
> > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build
> > from source, and test. Then please vote:
> >
> > [ ] +1 Release this package as nifi-1.10.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
>

Re: [ANNOUNCE] New Apache NiFi Committer Rob Fellows

[Matt Gilman]

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!
> >>
> >> On Wed, Sep 25, 2019 at 9:29 AM Andrew Lim 
> >> wrote:
> >>
> >>> Congrats Rob!
> >>>
> >>>
>  On Sep 24, 2019, at 7:56 PM, Tony Kurc  wrote:
> 
>  Apache NiFi community,
>  On behalf of the Apache NiFI PMC, I am very pleased to announce that
> >> Rob
>  has accepted the PMC's invitation to become a committer on the Apache
> >>> NiFi
>  project. We greatly appreciate all of Rob's hard work and generous
>  contributions to the project. We look forward to his continued
> >>> involvement
>  in the project.
> 
>  What stood out with Rob are his regular code contributions and reviews
> >> on
>  many parts of the project to include NiFi, NiFi FDS, and NiFi Registry
>  since early this year. Additionally, he's been doing the
>  not-always-glamorous work of helping verify releases, which was a huge
>  assist in getting NiFi 1.9.1, NiFi Registry 0.4.0 and 0.5.0, and NiFi
> >> FDS
>  0.2.0 out to the community.
> 
>  Welcome and congratulations!
>  Tony
> >>>
> >>>
> >>
>

Re: Apache NiFi contributor access

[Matt Gilman]

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 add me to contributor list? My username is 'b.ganesh' .
>
>
>
> Thanks & Regards,
>
> Ganesh.B
>
>

Re: [VOTE] Release Apache NiFi Registry 0.5.0

[Matt Gilman]

+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 for the source release of Apache
> NiFi Registry nifi-registry-0.5.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1147
>
> The Git tag is nifi-registry-0.5.0-RC1
> The Git commit ID is 8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16
>
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16
>
> Checksums of nifi-registry-0.5.0-source-release.zip:
> SHA256: 804948c2f3d6d32f88c37c1827d1c9c2d1f842f0ef7e7d953d24e76b152a093b
> SHA512:
> 0ae202b64ad3b3ab3dadb71b9dea210ac4c8eb1cf3922f10a71d175df75ec069e8a039bcc961d1969a6ac7417da4cc5bd4d0cc1e8515d88be6bd55b7c8c9bce9
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 28 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12345561
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.5.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> Then please vote:
>
> [ ] +1 Release this package as nifi-registry-0.5.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

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

[Matt Gilman]

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 the ID
token claimset (not the access token) which we honor in the token that NiFi
generates internally.

NiFi will only use the access token to invoke the User endpoint if the
email claim is not included in the ID token's claimset. The access token is
not saved or persisted by NiFi because we do not need to invoke any other
APIs from the identity provider.

It's likely that there are some improvements that could be made here. From
reading the spec, it appears that the intent of the refresh token is to
obtain a new access token. It's not clear whether this process should be
used to obtain a new id token. This is something that should be
investigated further. You could also check if there is another setting in
your identity provider for the ID Token Lifespan. Another option is that
NiFi could introduce a new property that allows the admin to configure how
long it wants to allow our 'sessions' to last.

Matt

On Wed, Aug 21, 2019 at 9:49 AM Kumara M S, Hemantha (Nokia - IN/Bangalore)
 wrote:

> Hi ,
>
> We have configured Nifi cluster and using OpenId Connect(keycloak<
> https://www.keycloak.org/>)  for user authentication.
> In Keycloak, here are some of configuration for token in realm settings
>
>   *   SSO Session Idle 30 Minutes
>   *   Access Token Lifespan 1 Minutes
>
>
> The issue is Nifi UI is giving error after every one minute "Session
> Expired : Your session has expired. Please press Ok to log in again., and
> this one just after : Unknown user with identity 'anonymous'. Contact the
> system administrator". Is this due to Nifi is checking session validity
> using only access_token?
>
> From Keycloak documentation
> https://www.keycloak.org/docs/latest/server_admin/index.html#_oidc-auth-flows
> access_token is short lived for security purpose. Isn't it Nifi should use
> refresh-token to check session validity and request new token that will
> renew session if required?
>
> Regards,
> Hemantha
>
>

Re: Adding Color to Connections

[Matt Gilman]

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 connection.
However, the concept of 'z-index' is not surfaced to the user. The action
available is 'Bring to front' and this affects the connection label.

One thing that's been discussed in the past is offering different modes (or
layers) based on specific use cases. Supporting different visualizations
when the user is configuring versus when they are monitoring could possibly
allow us to introduce more visualization while not conflicting with
existing ones.

Thanks

Matt

On Tue, Jul 30, 2019 at 12:37 PM Pierre Villard 
wrote:

> Hey,
>
> I like the idea but we need to have a clear differentiator compared to the
> situation where backpressure is enabled (and connection is coloured in
> red).
>
> Pierre
>
> Le mar. 30 juil. 2019 à 18:19, Peter Wicks (pwicks)  a
> écrit :
>
> > You know when you have a crazy complex flow, and it's hard sometimes to
> > even tell where things are going? Especially those failure conditions
> that
> > are all going back to a central Funnel or Port? I thought it would be
> > visually very helpful if you could add Color to your connections, using
> the
> > existing UI components in place for doing that.
> >
> > I have a working POC, https://issues.apache.org/jira/browse/NIFI-6504.
> > Which includes a screenshot and link to the branch.
> >
> > There are a number of open questions:
> >
> >   *   Should the markers (arrows) be colored also?
> >   *   Should there be an option to color other components such as
> funnel's
> > or ports?
> >   *   I've also considered adding some additional line formatting options
> > such as thickness and dashes, like the dashed green lines you see when
> > creating a new relationship, or the extra thick lines that represent
> > multiple relationships use now.
> >   *   Should there be an option to adjust connection z-index so that
> users
> > can make sure a connection isn't overlapping things in a weird way.
> >
> > The goal of this ticket is fully on making it easier and faster for users
> > to visually understand a flow. Any feedback is appreciated!
> >
> > Thanks,
> >   Peter
> >
>

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

[Matt Gilman]

+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 demo app works as expected
>
> Unfortunately majority of npm scripts are broken on windows, however I
> could make them run and test the app with some minor changes. JIRA issue:
> https://issues.apache.org/jira/browse/NIFI-6481
>
> + 1 (non-binding)
>
> András
>
> On Wed, Jul 24, 2019 at 11:41 AM Adam Kocsis  >
> wrote:
>
> > * Verified the git commit
> > * Verified the signature
> > * Verified the hashes
> > * Verified the build
> > * Verified README
> > * Verified the demo app works as expected
> >
> > + 1 (non-binding)
> >
> > Cheers,
> > Adam
> >
> > On Wed, Jul 24, 2019 at 3:33 AM Robert Fellows 
> > wrote:
> >
> > > * Verified the signature
> > > * Verified the hashes
> > > * Verified the build
> > > * Verified README
> > > * Verified the demo app works as expected
> > > * Successfully npm link'd @nifi-fds/core in nifi-registry, worked with
> > > documented updates.
> > >
> > > + 1 (non-binding)
> > >
> > >
> > > -- Rob Fellows
> > >
> > > On Tue, Jul 23, 2019 at 4:07 PM Scott Aslan 
> > wrote:
> > >
> > > > Hello,
> > > >
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > >
> > > > NiFi Flow Design System 0.2.0.
> > > >
> > > >
> > > > The source zip, including signatures, etc. can be found at:
> > > >
> > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.2.0/
> > > >
> > > >
> > > > The Git tag is NIFI-FDS-0.2.0-RC2
> > > >
> > > > The Git commit ID is 0b2443fce830a69f45c2d096872f84871e814d17
> > > >
> > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=0b2443fce830a69f45c2d096872f84871e814d17
> > > >
> > > >
> > > > Checksums of nifi-fds-0.2.0-source-release.zip:
> > > >
> > > > SHA1: d11a7bbd4bcb1a9fc09f69d0a87ba3c26c20318d
> > > >
> > > > SHA256:
> > 6dd0d9f9e09e57c85ea435e282118b1289fe7ebbeb6cd987aeeafc895815431f
> > > >
> > > > SHA512:
> > > >
> > > >
> > >
> >
> 34110b6f06c2bd21696a83f69f7d0d6840b669408e4c12cf0a6101b6596e977fa4dfb4b62ade5104f4ad7df369a278535e4bb6b65fb89dd793140d748f70c0d1
> > > >
> > > >
> > > > Release artifacts are signed with the following key:
> > > >
> > > > https://people.apache.org/keys/committer/scottyaslan.asc
> > > >
> > > >
> > > > KEYS file available here:
> > > >
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > >
> > > > 36 issues were closed/resolved for this release:
> > > >
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343453&projectId=12316020
> > > >
> > > >
> > > > Release note highlights can be found here:
> > > >
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.2.0
> > > >
> > > >
> > > > The vote will be open for 72 hours.
> > > >
> > > >
> > > > Please download the release candidate and evaluate the necessary
> items
> > > >
> > > > including checking hashes, signatures, build from source, and test.
> > > >
> > > >
> > > > The please vote:
> > > >
> > > >
> > > > [ ] +1 Release this package as nifi-fds-0.2.0
> > > >
> > > > [ ] +0 no opinion
> > > >
> > > > [ ] -1 Do not release this package because...
> > > >
> > >
> > >
> > > --
> > > ---
> > > Rob Fellows
> > >
> >
>

Re: [DISCUSS] Apache NiFi FDS 0.2.0

[Matt Gilman]

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 wanted to discuss releasing Apache NiFi FDS 0.2. in the coming
> > week or two. We have some updates to the specification as well as some
> very
> > useful updates to our build process. We also have upgraded to the latest
> > versions of Angular, jQuery, Covalent, and rxjs.
> >
> > If everyone is amenable to a release, I will RM unless anyone else would
> > like
> > to take those duties.
> >
> > Best Regards,
> > Scott Aslan
> >
>

Re: [VOTE] Release Apache NiFi Registry 0.4.0

[Matt Gilman]

+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 release of Apache
> NiFi Registry nifi-registry-0.4.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1145
>
> The Git tag is nifi-registry-0.4.0-RC1
> The Git commit ID is 4d7add09cd915b20dcc9959b49ecdf202d5eac2a
>
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=4d7add09cd915b20dcc9959b49ecdf202d5eac2a
>
> Checksums of nifi-registry-0.4.0-source-release.zip:
> SHA256: a8753372fbc24f7d293df6205c465edee7a4167d835811e84e27df3e609d2be1
> SHA512:
> 70ade1ba2dcf5363b6568669080a3607e5dfd3dffd28651ba5f6961db835e0f61ff7f9758757358800774e4e1063cdcfdd5d44a712a845e34052544cfce9b047
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 37 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12344183
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.4.0
>
> The vote will be open for 96 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> Then please vote:
>
> [ ] +1 Release this package as nifi-registry-0.4.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

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

[Matt Gilman]

+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,
>
> I am pleased to be calling this vote for the source release of Apache
> NiFi NAR Maven Plugin 1.3.1.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1144
>
> The Git tag is nifi-nar-maven-plugin-1.3.1-RC1
> The Git commit ID is 51deb8a070ef2b9f0041c2b6448b72de67f91822
>
> https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=51deb8a070ef2b9f0041c2b6448b72de67f91822
>
> Checksums of nifi-nar-maven-plugin-1.3.1-source-release.zip:
> SHA256: 48f2b3e361d7e45c79a659bfcf7a56a88278411f3686d2da800c58858c742637
> SHA512:
> c0ace13e7d7f7dd4468c7ac71f1dddc098393481cd1096c7479a48fb215ef47197969da50edb987b182592b988368104d58ec26a21ba4beea2a4db46b6dca4eb
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 1 issue was closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345484&styleName=&projectId=12316020
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion1.3.1
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build from source, and test.
> Then please vote:
>
> [ ] +1 Release this package as nifi-nar-maven-plugin-1.3.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

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

[Matt Gilman]

+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 AM Aldrin Piri  wrote:

> +1, binding
>
> notes:
> signature and hashes looked good
> build and contrib check good
> performed build of NiFi using generated NAR and didn't notice any
> peculiarities with typical operations.  NARs included the anticipated
> descriptor file and its contents looked good
>
>
>
> On Thu, May 2, 2019 at 10:29 AM Kevin Doran  wrote:
>
> > +1 (binding)
> >
> > Ran through the steps in the release helper guide and verified the new
> > metadata files are being written to the generated in NARs.
> >
> > Thanks for RM'ing, Bryan!
> >
> > On Tue, Apr 30, 2019 at 12:03 PM Bryan Bende  wrote:
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi NAR Maven Plugin 1.3.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1142
> > >
> > > The Git tag is nifi-nar-maven-plugin-1.3.0-RC1
> > > The Git commit ID is 84b66de25e5f1c0df66a4c8a0d1cbf00390aae18
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi-maven.git;a=commit;h=84b66de25e5f1c0df66a4c8a0d1cbf00390aae18
> > >
> > > Checksums of nifi-nar-maven-plugin-1.3.0-source-release.zip:
> > > SHA256:
> ff4ba1879e4b10bf4e8808363438f8082508e60b7539c9c32a5097982e470f3c
> > > SHA512:
> >
> 8b15553f5f4a5469f514a7d84c924f4ae27d3a0cc029217eb42923136e13e1074df4f1bccc80ef0def6b59b10dd85932a5ce2b93aaf918385b7798719518ad56
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/bbende.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 5 issues were closed/resolved for this release:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12340213
> > >
> > > Release note highlights can be found here:
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion1.3.0
> > >
> > > The vote will be open for 72 hours.
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> > > Then please vote:
> > >
> > > [ ] +1 Release this package as nifi-nar-maven-plugin-1.3.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> >
>

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

[Matt Gilman]

+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.9.2.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-
>
> The Git tag is nifi-1.9.2-RC2
> The Git commit ID is 11320acfbaab1a3579bd8f7545473d6984472d77
>
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=11320acfbaab1a3579bd8f7545473d6984472d77
>
> Checksums of nifi-x.y.z-source-release.zip:
> SHA256: 1f666c30171e2b7be847a3a852e9176420fd0176537f3ce6428b786a6d24f456
> SHA512:
>
> f65b81976a9811017348f9e8340faff3a29b029878845dd509db98eb7449752c8ef0bdbf5d1f67635636bb08be28086015442f546821eebf76b499cebf1a386b
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/joewitt.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 11 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12345213
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.9.2
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
>
> [ ] +1 Release this package as nifi-1.9.2
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: [DISCUSS] NiFi and Java 11

[Matt Gilman]

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  wrote:

> I created a JIRA [1] to track the developer documentation changes.  Andy,
> thanks for pointing out the specific links; I've added them to the JIRA.
>
> [1] https://issues.apache.org/jira/browse/NIFI-6187
>
> On Wed, Apr 3, 2019 at 11:23 PM Sivaprasanna 
> wrote:
>
> > Yep. Adding to GitHub template is a great idea.
> >
> > On Thu, 4 Apr 2019 at 5:27 AM, Andy LoPresto 
> wrote:
> >
> > > We should add that to the Developer Guide [1], Contributor Guide [2],
> > note
> > > it in the Migration Guide [3] when it takes effect, and include it in
> the
> > > GitHub PR template as well.
> > >
> > > [1] https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html <
> > > https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html>
> > > [2] https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide
> <
> > > https://cwiki.apache.org/confluence/display/NIFI/Contributor+Guide>
> > > [3]
> https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance
> > <
> > > https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance>
> > >
> > >
> > > Andy LoPresto
> > > alopre...@apache.org
> > > alopresto.apa...@gmail.com
> > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > >
> > > > On Apr 3, 2019, at 1:16 PM, Sivaprasanna 
> > > wrote:
> > > >
> > > > Sounds good to me.
> > > >
> > > > So contributors who bring in new changes are expected to write the
> code
> > > > that should be compatible with both Java 8 as well as Java 11, right?
> > > >
> > > > Do we see anything that we should have in our site that would help
> the
> > > > contributors/users with this change? Something like a document that
> > > > explains best practices which a developer should follow so that the
> > > change
> > > > which the developer is bringing in should run fine in both 8 and 11.
> > > >
> > > > -
> > > > Sivaprasanna
> > > >
> > > > On Thu, 4 Apr 2019 at 12:18 AM, Pierre Villard <
> > > pierre.villard...@gmail.com>
> > > > wrote:
> > > >
> > > >> Sounds good to me as well. Given the latest news on Java 8, having
> > the 2
> > > >> PRs merged in would be great!
> > > >>
> > > >> Thanks,
> > > >> Pierre
> > > >>
> > > >> Le mer. 3 avr. 2019 à 20:34, Joe Witt  a écrit
> :
> > > >>
> > > >>> Jeff
> > > >>>
> > > >>> This seems very reasonable and thorough to me.
> > > >>>
> > > >>> The only short term implication that we'd have to buy into then is
> > that
> > > >> PRs
> > > >>> going forward need to be able to build on both Java 8 and 11 which
> > > seems
> > > >> a
> > > >>> very fair way to bridge toward moving to Java 11 as the base
> > > requirement
> > > >> in
> > > >>> the next major release of NiFi (2.x).
> > > >>>
> > > >>> Thanks
> > > >>> Joe
> > > >>>
> > > >>> On Wed, Apr 3, 2019 at 2:19 PM Jeff  wrote:
> > > >>>
> > >  I'm reaching out to the community today to propose a plan for
> moving
> > >  forward with NiFi on Java 11.
> > > 
> > >  There are currently two PRs that deal with Java 11 compatibility.
> > The
> > >  first PR allows NiFi built on Java 8 to be run on Java 11 [1].
> The
> > > >>> second
> > >  PR allows NiFi to be built on Java 11 and run on Java 11 [2].
> There
> > > >> are
> > > >>> a
> > >  lot of changes in the second PR, and it will require a lot of
> > testing
> > > >> due
> > >  to the breadth of changes from dependency upgrades.  Please take a
> > > look
> > > >>> at
> > >  both of these PRs.  The earlier we can get feedback, the sooner we
> > can
> > > >>> get
> > >  Java 11 compatibility in an Apache NiFi release.
> > > 
> > >  I would to discuss with the community the following plan for
> > upcoming
> > > >>> NiFi
> > >  releases as they pertain to Java 11:
> > > 
> > >  For the 1.x release line, from either 1.10 or 1.11 (depending on
> > when
> > > >>> these
> > >  two PRs are merged to master) and onward, NiFi will be compatible
> > with
> > > >>> both
> > >  Java 8 and 11 for building and running NiFi:
> > > 
> > >    - Build on Java 8, run on Java 8
> > >    - Build on Java 8, run on Java 11
> > >    - Build on Java 11, run on Java 11
> > > 
> > >  The 1.x release line will contain convenience builds for Java 8,
> and
> > > >> will
> > >  NOT contain convenience builds created from Java 11.  Users that
> > want
> > > >> to
> > >  run NiFi 1.1x.y on Java 11 with Java 11 bytecode will have to
> build
> > > >> from
> > >  the released source code.
> > > 
> > >  Once the Java 11 compatibility features [1] [2] are merged to
> > master,
> > > >> PR
> > >  reviews will require building and testing with Java 8 and Java 11
> > > >> before
>

Re: global and component access policies

[Matt Gilman]

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 is
different from how component policies override ancestor policies. This
choice was made since it allowed for folks to define an administrator for
all things and local/component level administrators.

Matt

On Fri, Feb 22, 2019 at 3:03 PM Mark Bean  wrote:

> 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 access
> due to the global level policy.
>
> Is this correct/desired behavior?
>
> It seems to me the component level access policies should allow the ability
> for a global level policy to be overridden for a given component(s).
>

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

[Matt Gilman]

+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-loading NARs
>
> Minor note - I think it was mentioned already, but the source NOTICE
> still has the year as 2018.
>
> On Tue, Feb 19, 2019 at 12:33 PM Mike Thomsen 
> wrote:
> >
> > +1 (binding)
> >
> > Verified checksums, etc. and ran some simple flows. Didn't find anything
> > broken.
> >
> > On Tue, Feb 19, 2019 at 10:08 AM Mark Payne 
> wrote:
> >
> > > +1 (binding)
> > >
> > > Verified signature
> > > Upgraded cluster that ran 1.9.0-RC1. Started up without issue and has
> been
> > > running for about 48 hours without a problem.
> > > All issues raised appear to have been addressed in RC2. Flows consist
> of
> > > Site-to-Site, Load-Balanced Connections, Record-oriented
> > > processors, heavy Kafka integration.
> > >
> > > Thanks
> > > -Mark
> > >
> > >
> > > > On Feb 19, 2019, at 9:42 AM, Otto Fowler 
> > > wrote:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > - Verified signature
> > > > - Verified hashes
> > > > - Verified the build and tests were successful
> > > > - Verified Git commit ID
> > > > - Binary starts as expected
> > > >
> > > >
> > > > On February 16, 2019 at 22:50:46, Joe Witt (joew...@apache.org)
> wrote:
> > > >
> > > > +1 (non-binding)
> > > >
> > > > - Verified signature
> > > > - Verified hashes
> > > > - Verified the build and tests were successful
> > > > - Verified Git commit ID
> > > > - Binary starts as expected
> > >
> > >
>

Re: Advanced UI button on Update Attributes

[Matt Gilman]

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/apache/nifi/blob/98aabf2c50f857efc72fd6f2bfdd9965b97fa195/nifi-nar-bundles/nifi-update-attribute-bundle/nifi-update-attribute-ui/src/main/webapp/WEB-INF/jsp/worksheet.jsp#L171

For 2, we are utilizing a library (CodeMirror) to make a rich editor. If
you want to just use a standard textarea, you'll need to update the
worksheet.jsp by adding a standard textarea in the corresponding div (which
CodeMirror uses to house the dynamically created rich editor) and update
the necessary places in the backing JS. Those changes would be around here.

https://github.com/apache/nifi/blob/98aabf2c50f857efc72fd6f2bfdd9965b97fa195/nifi-nar-bundles/nifi-update-attribute-bundle/nifi-update-attribute-ui/src/main/webapp/js/application.js#L149

Hope this helps

Matt

On Wed, Jan 9, 2019 at 11:23 AM DAVID SMITH
 wrote:

> Koji
>
> Thanks for the reply, I found it about 30 minutes before I saw your
> answer, this now works I have Advanced UI on my test processor. I am now
> amending the UI to try to get it to work/look and feel slightly
> differently, however, I now have a couple of questions:
>
> 1) I can change the labels for Rules, Conditions, Actions for ones that I
> want but I cannot find out where to change the header 'Expression' in the
> conditions panel or Attribute & Value in the Actions panel, I have done a
> grep through the code and cannot find out how these are populated ?  I have
> amended the following couple of lines in the application.js file but it
> makes no difference, can anyone help?
>
>   // initialize the actions grid
> var actionsColumns = [
> {id: "start", name: "Start", field: "start", sortable: true,
> cssClass: 'pointer', editor: ua.getCustomLongTextEditor, validator:
> ua.requiredFieldValidator},
> {id: "stop", name: "Stop", field: "stop", sortable: true,
> cssClass: 'pointer', editor: ua.getCustomLongTextEditor, validator:
> ua.requiredFieldValidator}
> ];
>
> 2) When I bring up the add actions dialog, I have changed the labels to
> Start and Stop, now I want to change the type of input box used for the
> value (now Stop) to the same type that is used for the attribute (now
> Start), I guess it is the way the DIV is set up in the worksheet.jsp but
> any help would be appreciated.
>
>
>
> 
> On Mon, 7/1/19, Koji Kawamura  wrote:
>
>  Subject: Re: Advanced UI button on Update Attributes
>  To: "dev" 
>  Date: Monday, 7 January, 2019, 3:00
>
>  Probably you've already found
>  a solution, but just in case, did you
>  update
>  nifi-processor-configuration file, too?
>
>  
> nifi-update-attribute-ui/src/main/webapp/META-INF/nifi-processor-configuration
>
>  Thanks,
>  Koji
>
>  On Thu, Jan 3, 2019 at 7:29
>  PM DAVID SMITH
>  
>  wrote:
>  >
>  > Hi
>  > I am looking to create a bespoke processor
>  based very loosely on the Update Attribute processor set, I
>  have taken a copy of the update attribute bundle and changed
>  the name of the bundle and its components to
>  nifi-test-build-processor, nifi-test-build-model etc, I have
>  also amended the pom files to reference these new names.
>  However, when I build the new test processor set, it builds
>  and loads in NiFi 1.8.0 but the Advanced button has
>  disappeared in the UpdateAttribute processor configuration.
>  Can anyone tell me what I have missed, I have done this once
>  before but I can't remember what the answer is?
>  > Many thanksDave
>

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

[Matt Gilman]

+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 Apache NiFi
> nifi-1.8.0.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1135
>
> The Git tag is nifi-1.8.0-RC3
> The Git commit ID is 98aabf2c50f857efc72fd6f2bfdd9965b97fa195
>
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=98aabf2c50f857efc72fd6f2bfdd9965b97fa195
>
> Checksums of nifi-1.8.0-source-release.zip:
> SHA256: 6ec21c36ebb232f344493a4aeb5086eed0c462c576e11a79abed8149bc8b65c3
> SHA512:
>
> 846aecd4eb497a3b7dee7d1911b02453b8162b6c87e39f3df837744a478212e2e3e3615921079d29c2804671f26ecd05b04ce46a4bb69e8911fc185e27be9c24
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/jstorck.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 209 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12343482
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.8.0
>
> The vote will be open for 72 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
>
> [ ] +1 Release this package as nifi-1.8.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
>

Re: JSTL support in nifi-web-ui

[Matt Gilman]

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, Karthikeyan J  wrote:

> Hello,
>
> I am doing some UI customizations
> on nifi-nar-bundles/nifi-framework-bundle/nifi-
> framework/nifi-web/nifi-web-ui
> folder for our needs.
>
> As part of this, I have introduced JSTL tablib in canvas.jsp file.
>
> <%@ page contentType="text/html" pageEncoding="UTF-8" session="false" %>
> <%@ taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"; %>
>
> After the changes, I built and started the nifi. When I access
> http://localhost:8080/nifi link, I am getting the following exception.
>
> HTTP ERROR 500
> Problem accessing /nifi/. Reason:
>
> Server Error
> Caused by:
> javax.servlet.ServletException: org.apache.jasper.JasperException: The
> absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in
> either web.xml or the jar files deployed with this application
> at
> org.eclipse.jetty.server.handler.HandlerCollection.
> handle(HandlerCollection.java:138)
> at
> org.eclipse.jetty.server.handler.gzip.GzipHandler.
> handle(GzipHandler.java:561)
> at org.eclipse.jetty.server.handler.HandlerList.handle(
> HandlerList.java:52)
> at
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(
> HandlerWrapper.java:132)
> at org.eclipse.jetty.server.Server.handle(Server.java:564)
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:320)
> at
> org.eclipse.jetty.server.HttpConnection.onFillable(
> HttpConnection.java:251)
> at
> org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(
> AbstractConnection.java:279)
> at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:110)
> at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124)
> at
> org.eclipse.jetty.util.thread.Invocable.invokePreferred(
> Invocable.java:122)
> at
> org.eclipse.jetty.util.thread.strategy.ExecutingExecutionStrategy.invoke(
> ExecutingExecutionStrategy.java:58)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.
> produceConsume(ExecuteProduceConsume.java:201)
> at
> org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(
> ExecuteProduceConsume.java:133)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
> QueuedThreadPool.java:672)
> at
> org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(
> QueuedThreadPool.java:590)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.apache.jasper.JasperException: The absolute uri:
> http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or
> the jar files deployed with this application
> at
> org.apache.jasper.compiler.DefaultErrorHandler.jspError(
> DefaultErrorHandler.java:55)
> at
> org.apache.jasper.compiler.ErrorDispatcher.dispatch(
> ErrorDispatcher.java:293)
> at
> org.apache.jasper.compiler.ErrorDispatcher.jspError(
> ErrorDispatcher.java:80)
> at
> org.apache.jasper.compiler.TagLibraryInfoImpl.generateTldResourcePath(
> TagLibraryInfoImpl.java:251)
> at
> org.apache.jasper.compiler.TagLibraryInfoImpl.(
> TagLibraryInfoImpl.java:122)
> at org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:434)
> at org.apache.jasper.compiler.Parser.parseDirective(Parser.java:492)
> at org.apache.jasper.compiler.Parser.parseElements(Parser.java:1448)
> at org.apache.jasper.compiler.Parser.parse(Parser.java:145)
> at
> org.apache.jasper.compiler.ParserController.doParse(
> ParserController.java:244)
> at
> org.apache.jasper.compiler.ParserController.parse(
> ParserController.java:105)
> at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:201)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:372)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:349)
> at org.apache.jasper.compiler.Compiler.compile(Compiler.java:333)
> at
> org.apache.jasper.JspCompilationContext.compile(
> JspCompilationContext.java:600)
> at
> org.apache.jasper.servlet.JspServletWrapper.service(
> JspServletWrapper.java:368)
> at org.apache.jasper.servlet.JspServlet.serviceJspFile(
> JspServlet.java:385)
> at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:329)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.
> doFilter(ServletHandler.java:1634)
> at org.apache.nifi.web.server.JettyServer$2.doFilter(
> JettyServer.java:1042)
> at
> org.eclipse.jetty.servlet.ServletHandler$CachedChain.
> doFilter(ServletHandler.java:1621)
> at
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:541)
> at
> org.eclipse.jetty.server.handler.ScopedHandler.handle(
> ScopedHandler.java:143)
> at
> org.eclipse.jetty.security.SecurityHandler.handle(
> SecurityHandler.java:566)
> at

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

[Matt Gilman]

Peter,

I just re-read your note and I realize that I may have misinterpreted your
question. I thought that you were asking to only enforce WRITE permissions
on the parent group. If this was the case, my previously stated concerns
apply. If we're looking to retain the component based checks and
additionally introduce a check on the parent group then my concerns don't
apply. We certainly have other endpoints that concern multiple components
(like referencing controller services for instance) which require multiple
checks. However, they always include the primary component as a 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,
> possibly in the next major release. I do have some concerns about
> introducing it in the near term. NiFi employs a fine grain authorization
> model where policies on each component drive access decisions. These
> resources map to the REST API resources. We treat our REST APIs and
> corresponding data models as public interfaces from a compatibility
> perspective (unless called out as non-guaranteed). Currently, clients can
> perform this action by changing the [x, y] coordinates on the component,
> invoking the component's REST endpoint, and being authorized to perform
> this action. The concerns I have are regarding this backward compatibility
> and existing clients and whether the update would leave the REST API and
> authorization scheme understandable/consumable. For instance, requiring the
> client to know that updating field A requires policy Y but updating field B
> requires policy Z.
>
> Matt
>
>
> On Fri, Jul 27, 2018 at 3:11 PM, Andy LoPresto 
> wrote:
>
>> Peter,
>>
>> I vaguely recall the conversations around (similar, not exactly the same)
>> permissions at the time this was implemented, and it was decided 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 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>>
>> On Jul 27, 2018, at 9:32 AM, Peter Wicks (pwicks) 
>> wrote:
>>
>> While experimenting with permissions, I found that if I have no
>> permissions to a process group, but do have permissions to a child that
>> lives in that group, I can move that child around on the UI.
>>
>> I know that in the object model the x,y position values are part of the
>> child, which I have access to; but in this scenario it feels like I'm
>> allowed to modify things in a group where I have no permissions. I propose
>> that users can't move (x,y) objects if they do not have modify access to
>> the parent group. Thoughts?
>>
>> --Peter
>>
>>
>>
>

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

[Matt Gilman]

Please file the JIRA. I'm definitely not opposed to this change long-term,
possibly in the next major release. I do have some concerns about
introducing it in the near term. NiFi employs a fine grain authorization
model where policies on each component drive access decisions. These
resources map to the REST API resources. We treat our REST APIs and
corresponding data models as public interfaces from a compatibility
perspective (unless called out as non-guaranteed). Currently, clients can
perform this action by changing the [x, y] coordinates on the component,
invoking the component's REST endpoint, and being authorized to perform
this action. The concerns I have are regarding this backward compatibility
and existing clients and whether the update would leave the REST API and
authorization scheme understandable/consumable. For instance, requiring the
client to know that updating field A requires policy Y but updating field B
requires policy Z.

Matt


On Fri, Jul 27, 2018 at 3:11 PM, Andy LoPresto  wrote:

> Peter,
>
> I vaguely recall the conversations around (similar, not exactly the same)
> permissions at the time this was implemented, and it was decided 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 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Jul 27, 2018, at 9:32 AM, Peter Wicks (pwicks) 
> wrote:
>
> While experimenting with permissions, I found that if I have no
> permissions to a process group, but do have permissions to a child that
> lives in that group, I can move that child around on the UI.
>
> I know that in the object model the x,y position values are part of the
> child, which I have access to; but in this scenario it feels like I'm
> allowed to modify things in a group where I have no permissions. I propose
> that users can't move (x,y) objects if they do not have modify access to
> the parent group. Thoughts?
>
> --Peter
>
>
>

Re: [VOTE] Release Apache NiFi 1.7.1

[Matt Gilman]

+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 specified in the subjectAlternativeNames. Once I
issued new certificates with these entries all was good. Since this check
is now more strict, we should probably call this out in case others happen
to be using certificates like I was.

Thanks for RMing Andy!

Matt

On Fri, Jul 13, 2018 at 3:44 PM, Mark Payne  wrote:

> +1 (binding).
>
> Verified checksums and hashes.
> Verified full build with contrib-check.
> Verified that the app starts and provides the basic functionalities.
> Verified that wildcard certificates now work in clustered mode.
> Verified that the recursively referenced Controller Services now behave as
> expected, not throwing StackOverflowException.
>
> Many thanks for handling the RM duties, Andy!
>
> Thanks
> -Mark
>
>
> On Jul 13, 2018, at 2:24 PM, Andy LoPresto  lopre...@apache.org>> wrote:
>
> Peter,
>
> Thanks for validating. The tag was pushed to the official repository [1]
> but not mirrored to github yet. For the official release, it will be there.
>
> [1] https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=tag;h=
> 411983dbafaaae8d76a2d7a4ae4b8d1177fae1eb
>
> Andy LoPresto
> alopre...@apache.org
> alopresto.apa...@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
> On Jul 13, 2018, at 9:55 AM, James Wing mailto:jvwin
> g...@gmail.com>> wrote:
>
> +1 (binding).  Ran through the release helper, checked license, notice,
> readme files, and tested the resulting binary.
>
> Thanks for putting this together, Andy.
>
> On Thu, Jul 12, 2018 at 2:00 PM Andy LoPresto  > wrote:
>
> Hello,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> nifi-1.7.1.
>
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1131
>
> The Git tag is nifi-1.7.1-RC1
> The Git commit ID is 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>
> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 241e5411a24435ca2c39ab7bea1c5eb9ed195cb3
>
> Checksums of nifi-1.7.1-source-release.zip:
> SHA1: 92428e219f8792b886a2826119d3f70c98de52fe
> SHA256: e951a0a2c6b7f8e742b8ab126532ab2e02876ba8c1db34b858fb72718a9fa0e6
> SHA512:
> a37add06c3c4f2ae5294c9f7668e2e837d6b92095d8e349d18cb13a1748c
> 0e052632415e0fda148f55b61f6774bcdd487ee3d8b8125fe4d2345791da1fc7d8d9
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/alopresto.asc
>
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
> 13 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020&version=12343647
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.7.1
>
> The vote will be open for 96 hours.
> Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> from source, and test. Then please vote:
>
> [ ] +1 Release this package as nifi-1.7.1
> [ ] +0 no opinion
> [ ] -1 Do not release this package because…
>
> Andy LoPresto
> alopre...@apache.org
> *alopresto.apa...@gmail.com <
> alopresto.apa...@gmail.com>*
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
>
>
>

Re: I will contact you with one question.

[Matt Gilman]

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://issues.apache.org/jira/browse/NIFI-4535

On Tue, Jul 10, 2018 at 3:35 AM, 강전혁  wrote:

> Hello !
>
>
>
> My name is Jenhyuk Kang
>
>
>
> I will contact you with one question.
>
>
>
> I want change title
>
>
>
> ex) NiFi
>
>
>
>
>
> NiFi
>
>
>
> i found index.jsp,  header.jsp, canvas.jsp, canvas_jsp.java etc..
>
>
>
> I changed the title part, but it is still.
>
>
>
> help me !
>
>
> 블로그서명
> [image: 블로그]  강디너 블로그
> 
> 초보 프로그래머의 공부일기 
>

Re: [VOTE] Release Apache NiFi MiNiFi 0.5.0 RC2

[Matt Gilman]

+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 sigs and hashes. Looks good.
>
> On Fri, Jun 29, 2018, 6:59 PM Andy LoPresto  wrote:
>
> > +1, binding
> >
> > Verified all keys and checksums, ran through all the builds, verified
> > tests and contrib-check, and the existence of LICENSE/NOTICE/README at
> > appropriate locations. A couple minor points on the release process below
> > (and some other non-blocking issues that I will open as Jiras).
> >
> > * Now that MD5 is deprecated, I believe we agreed to provide a SHA-512
> > signature as well. The release guide should be updated to include this
> for
> > next time.
> > * The release helper should specify that LICENSE, NOTICE, and README are
> > in minifi-assembly/target*/minifi-0.5.0-bin/minifi-0.5.0/*
> >
> > Andy LoPresto
> > alopre...@apache.org
> > *alopresto.apa...@gmail.com *
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> >
> > On Jun 29, 2018, at 8:29 AM, Aldrin Piri  wrote:
> >
> > Hi folks,
> >
> > I worked with Jeremy to resolve the discrepancy and we were able to get
> the
> > commits/tag in question from the Maven release plugin pushed to the repo.
> >
> > The minifi-0.5.0-RC2 tag is correct in pointing to the source of the...
> > source commit 58b8c598c0866c8f1200164ab14f3df0d632d522 which was
> initiated
> > from the last commit on master, 05f516d3da33a0547ccfad34241450
> 4cdacd4a68.
> >
> > Links for reference:
> > tag:
> > * https://github.com/apache/nifi-minifi/tree/minifi-0.5.0-RC2
> > *
> >
> > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=
> shortlog;h=refs/tags/minifi-0.5.0-RC2
> >
> > RC2 branch commit:
> > *
> >
> > https://github.com/apiri/nifi-minifi/commit/
> 58b8c598c0866c8f1200164ab14f3df0d632d522
> > *
> >
> > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=
> 58b8c598c0866c8f1200164ab14f3df0d632d522
> >
> > --aldrin
> >
> >
> > On Fri, Jun 29, 2018 at 7:59 AM Jeff Zemerick 
> > wrote:
> >
> > +1 non-binding
> >
> > Built and ran MiNiFi and C2 without issues.
> >
> > On Thu, Jun 28, 2018 at 3:59 PM Aldrin Piri  wrote:
> >
> > +1, binding
> >
> > comments:
> > My vote is on the assumption there there was a slight mix up with tagging
> > and it can be easily remedied.  The
> > 05f516d3da33a0547ccfad342414504cdacd4a68
> > points to the last commit and a snapshot version.  This is correct from
> > where the release is started but does not capture the generated prepared
> > release artifacts.  I believe if that is pushed and referenced, we will
> > have what is packed in the source distribution, which is listed as 0.5.0,
> > non-snapshot.
> >
> > signature and hashes looked good
> > verified contrib, build, and tests of minifi, config-toolkit, and c2
> >
> > server
> >
> > verified transform functionality of config toolkit
> > verified consumption of transformed config in minifi and its successful
> > site to site transaction to nifi
> > verified interaction with c2 server with a file based provider
> >
> > On Thu, Jun 28, 2018 at 1:19 PM Jeremy Dyer 
> >
> > wrote:
> >
> >
> > Hello,
> >
> > I am pleased to call this vote for the source release of Apache NiFi
> >
> > MiNiFi
> >
> > minifi-0.5.0 RC2.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > *
> >
> > https://repository.apache.org/content/repositories/orgapachenifi-1130/
> >
> > <
> >
> > https://repository.apache.org/content/repositories/orgapachenifi-1130/
> >
> > *
> >
> > The Git tag is minifi-0.5.0-RC2
> > The Git commit ID is 05f516d3da33a0547ccfad342414504cdacd4a68
> > *
> >
> >
> >
> > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=
> 05f516d3da33a0547ccfad342414504cdacd4a68
> >
> > <
> >
> >
> >
> > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=
> 05f516d3da33a0547ccfad342414504cdacd4a68
> >
> > *
> >
> > *
> >
> >
> >
> > https://github.com/apache/nifi-minifi/commit/
> 05f516d3da33a0547ccfad342414504cdacd4a68
> >
> > <
> >
> >
> >
> > https://github.com/apache/nifi-minifi/commit/
> 05f516d3da33a0547ccfad342414504cdacd4a68
> >
> > *
> >
> >
> > wget
> >
> >
> >
> >
> > https://repository.apache.org/content/repositories/
> orgapachenifi-1130/org/apache/nifi/minifi/minifi/0.5.0/
> minifi-0.5.0-source-release.zip
> >
> >
> > Checksums of minifi-0.5.0-source-release.zip:
> > SHA1: be624db030aedd5c249e58c4c57d55ca917cd6ea
> > SHA256:
> >
> > 1f96ca7d8c2f52f9c15dad532065163f14cb01a2edbc783d4faa33656ff5ab88
> >
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/jeremydyer.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 16 issues were closed/resolved for this release:
> > *
> >
> >

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

[Matt Gilman]

+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
>
> * Stepped through the release guide to verify the sig, hashes, and commit
> ID
> * Checked for readme, notice, and license in source and target
> * Checked for the package version update changes
> * Ran the demo app – seems to be a slight delay initially loading up but
> all looks good
>
> Thanks for all your effort on this, Scott!
>
>
> On Tue, Jun 12, 2018 at 2:59 AM Pierre Villard <
> pierre.villard...@gmail.com>
> wrote:
>
> > +1, binding
> >
> > Went through the release helper guide and all looks good to me AFAICT.
> > I merged the PR from Andy and set the fix version to 0.2.0.
> > (could be a good idea to ask infra for a dedicated JIRA so we don't mix
> > things regarding version numbers?)
> >
> > Congrats on this first release and thanks to everyone involved!
> >
> > Pierre
> >
> > 2018-06-12 1:02 GMT+02:00 Andy LoPresto :
> >
> > > Verified the GPG signature (SHA-512 digest, excellent) and checksums.
> > > Ran through the build and deployed, testing the demo app.
> > > Verified the LICENSE, NOTICE, and README in the source and deployable
> > > application.
> > > Checked the versioning in package.json and package-lock.json (not a
> > > JS/node expert, but I think it’s right).
> > >
> > > (One tiny typo in the README, which I fixed in a PR).
> > >
> > > +1, binding
> > >
> > > Thanks for your continued work on this release, Scott.
> > >
> > >
> > > Andy LoPresto
> > > alopre...@apache.org
> > > *alopresto.apa...@gmail.com *
> > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69
> > >
> > > On Jun 11, 2018, at 1:50 PM, Scott Aslan 
> wrote:
> > >
> > > Hello,
> > >
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > >
> > > NiFi Flow Design System 0.1.0.
> > >
> > >
> > > The source zip, including signatures, etc. can be found at:
> > >
> > > https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/
> > >
> > >
> > > The Git tag is nifi-fds-0.1.0-RC3
> > >
> > > The Git commit ID is 4f62f3d4a4626f66011289c7f1346c082a932184
> > >
> > > *https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=
> > > commit;h=4f62f3d4a4626f66011289c7f1346c082a932184
> > >  > > commit;h=4f62f3d4a4626f66011289c7f1346c082a932184>*
> > >
> > >
> > > Checksums of nifi-fds-0.1.0-source-release.zip:
> > >
> > > SHA1:
> > >
> > > ce971d78cc0660299dcee2233bc22fa78e2940af
> > >
> > > SHA256:
> > >
> > > 7cb36f412b4147c0e071508f4f6d2ca76b2fe524382937d6552dbe7efe10a827
> > >
> > > SHA512:
> > >
> > > 11e9cf4a529862da528bd616124e57f567503c25820e4b70e72d3d53f16b
> > > fed7c0c97f05f7c390267d2163cdae2c6151dc6d9a9bdf6c11be8a6dca4409b3bd15
> > >
> > >
> > > Release artifacts are signed with the following key:
> > >
> > > https://people.apache.org/keys/committer/scottyaslan.asc
> > >
> > >
> > > KEYS file available here:
> > >
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > >
> > > 7 issues were closed/resolved for this release:
> > >
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > > ctId=12316020&version=12343357
> > >
> > >
> > > Release note highlights can be found here:
> > >
> > > https://cwiki.apache.org/confluence/display/NIFI/Release+
> > > Notes#ReleaseNotes-NiFiFlowDesignSystem0.1.0
> > >
> > >
> > > The vote will be open for 72 hours.
> > >
> > >
> > > Please download the release candidate and evaluate the necessary items
> > >
> > > including checking hashes, signatures, build from source, and test.
> > >
> > >
> > > The please vote:
> > >
> > >
> > > [ ] +1 Release this package as nifi-fds-0.1.0
> > >
> > > [ ] +0 no opinion
> > >
> > > [ ] -1 Do not release this package because...
> > >
> > >
> > >
> >
>

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

[Matt Gilman]

-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 not the package-lock.json. Because of this, the built artifacts that
ended up in the node_modules had a version of 0.0.0 (not 0.1.0). It may
make sense to render this version in the demo application to prevent this
in the future. There's an added benefit that we'd also know what version of
nifi-fds was being shown.

Matt

On Fri, Jun 8, 2018 at 8:03 PM, Scott Aslan  wrote:

> Hello,
>
>
> I am pleased to be calling this vote for the source release of Apache
>
> NiFi Flow Design System 0.1.0.
>
>
> The source zip, including signatures, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/nifi/nifi-fds/nifi-fds-0.1.0/
>
>
> The Git tag is nifi-fds-0.1.0-RC1
>
> The Git commit ID is 35423f267de0755087a274ece79c81ef1a4ee641
>
> https://git-wip-us.apache.org/repos/asf?p=nifi-fds.git;a=commit;h=
> 35423f267de0755087a274ece79c81ef1a4ee641
>
>
> Checksums of nifi-fds-0.1.0-source-release.zip:
>
> SHA1: 389b7bda654cfb9a79efa5f893eb37b9f73caaf5
>
> SHA256: b42de408e797df859ab8e11e39bd717c996df775179bfae82bf4392bb346a135
>
> SHA512:
> 3b1cca1d5c3cd1786fb54deaa9e9761feb1b8bd2b365658ecef302ba617d
> d3fe66766513d76ad8686ce7f87a25d6d6152ccdae1bf2dfb3d5dba3e352d53a4122
>
>
> Release artifacts are signed with the following key:
>
> https://people.apache.org/keys/committer/scottyaslan.asc
>
>
> KEYS file available here:
>
> https://dist.apache.org/repos/dist/release/nifi/KEYS
>
>
> 7 issues were closed/resolved for this release:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020&version=12343357
>
>
> Release note highlights can be found here:
>
> https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-NiFiFlowDesignSystem0.1.0
>
>
> The vote will be open for 72 hours.
>
>
> Please download the release candidate and evaluate the necessary items
>
> including checking hashes, signatures, build from source, and test.
>
>
> The please vote:
>
>
> [ ] +1 Release this package as nifi-fds-0.1.0
>
> [ ] +0 no opinion
>
> [ ] -1 Do not release this package because...
>

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

[Matt Gilman]

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 NiFi Flow Design System
> [1]
> > and although there are still a few 'in progress' issues ([3], [4], [5])
> I think
> > we are probably very close to an initial release focused on a reusable
> > platform providing a consistent set of UI/UX components across the NiFi
> > ecosystem.
> >
> > Since NiFi Registry will have a dependency on client code provided by
> the flow
> > design system, the first release of the flow design system would need to
> > occur before the next release of NiFi Registry that integrates with it.
> The
> > work on the NiFi Registry side is being done as part of NIFIREG-39 [2].
> >
> > Let me know if anyone has any thoughts or comments.  I'm happy to act as
> RM
> > if no one else is interested in doing so, and we can start the process of
> > going through JIRA to see what is left.
> >
> > Thanks,
> >
> > Scott
> >
> > [1] https://nifi.apache.org/fds.html
> > [2] https://issues.apache.org/jira/browse/NIFIREG-39
> > [3] https://issues.apache.org/jira/browse/NIFI-5219
> > [4] https://issues.apache.org/jira/browse/NIFI-5216
> > [5] https://issues.apache.org/jira/browse/NIFI-5240
>
> Glad to see the progress! FYI, the FDS link [1] appears to be broken (404
> Not
> Found)
>
> Regards,
>
> Andy I.C.
>
> [1] https://nifi.apache.org/fds.html
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQEcBAEBAgAGBQJbCEm2AAoJEG1+mBKNMpIDbhEH/2UdqgAh2F7F8rvIYIqPbX53
> Ucjk8SlCLSbmocS8vIx4SbIQamy6bEYgtdqPwUvyfm82QLUW2zDt+1WtHYVMNOlV
> dikiNIHRR/yqPCU8ZfNkyKJI0ajw+lvc/DSmH97TYsmmYw889lX/LfnLuObq0RG1
> pflvme1E7vDr0CFLSJ39qBnKeTL/AvVDINBXjmdDr/6LlK9Bw/XdHdkMnFZ4dpUF
> /mHeNfp+RtHyAHP+Igw1aqaSiNyRWArQlF/T3WHhR9kpyjq+Fca+bl5OMufKxjiq
> ATLU6UsoRbBDwmlf/ZOI+O/CKNfD+oHzKFSPpIVsxdkJHWp3huaJiuGyUlbxUhA=
> =q33Z
> -END PGP SIGNATURE-
>
>
>
> ​Sent from ProtonMail, Swiss-based encrypted email.​
>
>

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

[Matt Gilman]

+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 Apache NiFi Flow Design System.
>
> The name change reflects that nifi-fds is meant to establish a set of
> reusable UI components for the NiFi ecosystem, and that these components
> are not tied to a single design system or UI platform.
>
> I am a +1.
>
> The vote will be open for 72 hours and will be a majority rule vote.
>
> [ ] +1 Change the name to Apache NiFi Flow Design System
> [ ] +0 No opinion
> [ ] -1 Do not change the name because...
>
> [1]
> http://mail-archives.apache.org/mod_mbox/nifi-dev/201805.
> mbox/%3CCAGmW7OxAaazAYDs8_v%3DkwYPKtJp3tMDEJdyGztSFgcmdv%
> 3DAS4w%40mail.gmail.com%3E
>

Re: status bar counts on a cluster

[Matt Gilman]

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

On Wed, Apr 25, 2018 at 9:29 AM, Mark Bean  wrote:

> 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  wrote:
>
> > 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 coming from the Cluster Coordinator
> nor
> > the Primary Node. Both of those nodes are missing the configuration file
> > and have a count of 6 invalid processors. Also, no matter which node the
> UI
> > is using, the status bar count is always 4. So, the count is not coming
> > from the UI's host.
> >
> > Question: how does the status bar derive its information?
> >
> > Thanks,
> > Mark
> >
>

Re: Search for Controller Service UUID

[Matt Gilman]

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 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 design?
>
> Thanks,
> Mark
>

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

[Matt Gilman]

+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 OS X
> - confirmed that previous issues reported with RC1 and RC2 are fixed
> - tested secured/unsecured standalone/cluster deployments
>
> Minor remark for the RM documentation and the release helper guide. We're
> currently saying to run
> mvn clean install -Pcontrib-check,include-grpc
>
> I'd recommend to run all the existing "include" profiles to be on the safe
> side:
> mvn clean install -Pcontrib-check,include-grpc,
> include-atlas,include-ranger
>
> Pierre
>
>
>
> 2018-04-04 16:43 GMT+02:00 Marc :
>
> > +1 binding
> >
> >-- verified sigs and hashes.
> >-- confirmed a parallel build with tests
> >-- started secure cluster and interfaced with Apache NiFi MiNiFi C++
> >
> >
> >
> > On Wed, Apr 4, 2018 at 6:33 AM, Takanobu Asanuma  >
> > wrote:
> > > Thanks for all your efforts, Joe.
> > >
> > > +1(non-binding).
> > >  - Verified all hashes
> > >  - Succeeded "mvn -T 2.0C clean install -Prpm,generateArchives
> > -DskipTests"
> > >  - Started a secure cluster with three NiFi nodes and three ZK nodes
> > using Docker (Verified the whitelist feature)
> > >  - Verified some dataflows work fine
> > >
> > > -Takanobu Asanuma
> > >
> > > -Original Message-
> > > From: Joe Witt [mailto:joew...@apache.org]
> > > Sent: Wednesday, April 04, 2018 8:49 AM
> > > To: dev@nifi.apache.org
> > > Subject: [VOTE] Release Apache NiFi 1.6.0 (RC3)
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi nifi-1.6.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1124
> > >
> > > The Git tag is nifi-1.6.0-RC3
> > > The Git commit ID is f8466cb16d6723ddc3bf5f0e7f8ce8a47d27cbe5
> > > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > f8466cb16d6723ddc3bf5f0e7f8ce8a47d27cbe5
> > >
> > > Checksums of nifi-1.6.0-source-release.zip:
> > > SHA1: d1e1c24f9af809bf812982962b61d07df4f1131e
> > > SHA256: 1e5028d594bb402aa36460f1b826d4e8a664ad6f0538deed20286cbf3c62
> 1fb8
> > > SHA512: 8cb10cbafa6feeed712dbc0cf076496d6bc014276aab71383ff3481d8ea7
> > 19cf1f39766abc76c75ba58ffca747df3bd6d9bac82e410de1c78673dcd16a5ddfee
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/joewitt.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 162 issues were closed/resolved for this release:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12316020&version=12342422
> > >
> > > Release note highlights can be found here:
> > > https://cwiki.apache.org/confluence/display/NIFI/
> > Release+Notes#ReleaseNotes-Version1.6.0
> > >
> > > The vote will be open for 72 hours.
> > > Please download the release candidate and evaluate the necessary items
> > including checking hashes, signatures, build from source, and test.  The
> > please vote:
> > >
> > > [ ] +1 Release this package as nifi-1.6.0 [ ] +0 no opinion [ ] -1 Do
> > not release this package because...
> >
>

Re: Firefox - Slower movements when moving around the canvas

[Matt Gilman]

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.
Additionally, Firefox 59 seemed to be on par with Chrome 65.

Matt

On Tue, Apr 3, 2018 at 4:10 PM, Michael Moser  wrote:

> Adding a data point: using Firefox for Linux 64-bit, I see no difference
> between Firefox 58.0.2 and 59.0.2.  Neither exhibit a slow canvas with the
> NiFi UI.
>
> -- Mike
>
>
> On Tue, Apr 3, 2018 at 3:24 PM, Pierre Villard <
> pierre.villard...@gmail.com>
> wrote:
>
> > Yep, same here Mike, back to square one I guess...
> > One additional remark: paint event duration seems to be proportional with
> > the number of elements to paint on the UI. Not really surprising but just
> > wanted to add the info.
> >
> >
> > 2018-04-03 21:12 GMT+02:00 Mike Thomsen :
> >
> > > Found on Reddit that you can toggle OMTP using this:
> layers.omtp.enabled
> > >
> > > Disabled it and restarted. Didn't seem to do any good.
> > >
> > > On Tue, Apr 3, 2018 at 3:08 PM, Mike Thomsen 
> > > wrote:
> > >
> > > > Yeah, I'm using a Mac.
> > > >
> > > > On Tue, Apr 3, 2018 at 2:34 PM, Pierre Villard <
> > > > pierre.villard...@gmail.com> wrote:
> > > >
> > > >> I've been trying to debug this one and here are my findings so
> far...
> > > >>
> > > >> When debugging performance with the developer tools, the "Paint"
> event
> > > of
> > > >> the page is what is taking so long (between 3.5s to 5.5s (!!!) when
> I
> > > move
> > > >> from one place to another on the root canvas). Based on the release
> > note
> > > >> of
> > > >> Firefox 59.0 [1], I see that there is something new for Mac users
> > (Mike,
> > > >> are you also using a Mac?): "Improved graphics rendering using
> > > >> Off-Main-Thread Painting (OMTP) [2] for Mac users (OMTP for Windows
> > was
> > > >> released in Firefox 58)".
> > > >>
> > > >> So it seems to be related to this new feature(someone using Windows
> > > could
> > > >> help conf irming if it's also slow using Firefox 58.x.).
> > > >> I tried to find existing bugs but didn't find anything really
> > > relevant...
> > > >>
> > > >> [1] https://www.mozilla.org/en-US/firefox/59.0/releasenotes/
> > > >> [2] https://mozillagfx.wordpress.com/2017/12/05/off-main-
> > > thread-painting/
> > > >>
> > > >>
> > > >>
> > > >> 2018-04-03 16:00 GMT+02:00 Mike Thomsen :
> > > >>
> > > >> > I experienced it yesterday as well. I'm about to install a LTS
> > version
> > > >> of
> > > >> > Firefox so I can keep going there.
> > > >> >
> > > >> > While someone from the UI side figures this out, I think it should
> > be
> > > >> filed
> > > >> > as a bug report to Mozilla.
> > > >> >
> > > >> > On Sat, Mar 31, 2018 at 5:04 PM, Pierre Villard <
> > > >> > pierre.villard...@gmail.com
> > > >> > > wrote:
> > > >> >
> > > >> > > Just confirmed that behavior changed between Firefox 58.x and
> > 59.x.
> > > >> > > I'll let our UI gurus find the root cause and will probably use
> > > >> Chrome in
> > > >> > > the meantime :)
> > > >> > >
> > > >> > > 2018-03-31 22:02 GMT+02:00 Pierre Villard <
> > > >> pierre.villard...@gmail.com>:
> > > >> > >
> > > >> > > > Hi guys,
> > > >> > > >
> > > >> > > > I'm running on master, using Firefox (59.0.2), and it seems it
> > got
> > > >> > slower
> > > >> > > > to move around the canvas. In my case, I've around 10 PGs and
> > > >> around 50
> > > >> > > > processors. When trying to move from one place to another at
> the
> > > >> root
> > > >> > > > level, it's really slow and movement is intermittent/broken
> (not
> > > >> > fluid).
> > > >> > > > When accessing the same NiFi with Chrome, no issue at all.
> > > >> > > >
> > > >> > > > Problem is... I've also tried with a NiFi 1.5.0 and a NiFi
> > 1.3.0 I
> > > >> have
> > > >> > > > locally with various workflows, and it's the same with the
> older
> > > >> > > versions.
> > > >> > > >
> > > >> > > > Wondering if this could be related to the upgrade to Firefox
> > 59.x.
> > > >> > > >
> > > >> > > > Has anyone experienced the same?
> > > >> > > >
> > > >> > > > I can try to downgrade to Firefox 58.x to confirm but wanted
> to
> > > >> check
> > > >> > > with
> > > >> > > > the community first.
> > > >> > > >
> > > >> > > > Thanks!
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>

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

[Matt Gilman]

+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 check out
> * build and tests verified on CentOS 7 and OS X 10.12
> * ran some simple flows on each and things looked fine
>
> On Thu, Mar 29, 2018 at 1:06 AM, Sivaprasanna 
> wrote:
>
> > Thanks, Scott. That helped.
> >
> > On Thu, 29 Mar 2018 at 10:09 AM, James Wing  wrote:
> >
> > > +1 (binding).  Ran through the release helper, worked with a test flow.
> > > Thanks for putting this together.
> > >
> > > On Mon, Mar 26, 2018 at 8:34 PM, Joe Witt  wrote:
> > >
> > > > Hello,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > > NiFi nifi-1.6.0.
> > > >
> > > > The source zip, including signatures, digests, etc. can be found at:
> > > > https://repository.apache.org/content/repositories/
> orgapachenifi-1123
> > > >
> > > > The Git tag is nifi-1.6.0-RC2
> > > > The Git commit ID is b5935ec81a7cbc048820781ac62cd96bbea5b232
> > > > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > > b5935ec81a7cbc048820781ac62cd96bbea5b232
> > > >
> > > > Checksums of nifi-1.6.0-source-release.zip:
> > > > SHA1: 009f1e2e3c17e38f21f27170b9c06228d11653c0
> > > > SHA256: 39941a5b25427e2b4cc5ba8206084ff92df58863f29ddd097d4ac1e85424
> > beb9
> > > > SHA512: 1773417a48665e3cda22180ea7f401bc8190ebddbf3f7bc29831e46e7ab0
> > > > a07694c6e478d252fa573209d4a3c8132a522a8507b6a8784669ab7364847a07e234
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/joewitt.asc
> > > >
> > > > KEYS file available here:
> > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >
> > > > 146 issues were closed/resolved for this release:
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > projectId=12316020&version=12342422
> > > >
> > > > Release note highlights can be found here:
> > > > https://cwiki.apache.org/confluence/display/NIFI/
> > > > Release+Notes#ReleaseNotes-Version1.6.0
> > > >
> > > > The vote will be open for 72 hours.
> > > > Please download the release candidate and evaluate the necessary
> items
> > > > including checking hashes, signatures, build
> > > > from source, and test.  The please vote:
> > > >
> > > > [ ] +1 Release this package as nifi-1.6.0
> > > > [ ] +0 no opinion
> > > > [ ] -1 Do not release this package because...
> > > >
> > >
> >
>

Re: [VOTE] Release Apache NiFi 1.6.0

[Matt Gilman]

+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 release and run NiFi on Ubuntu
> 16.04.  It worked as expected with no new comments to add.
>
> -- Mike
>
>
> On Fri, Mar 23, 2018 at 4:02 PM, Scott Aslan 
> wrote:
>
> > +1 (binding)
> >
> > - Ran through release helper
> > - Setup secure NiFi and verified a test flow
> >
> > On Fri, Mar 23, 2018 at 3:29 PM, Bryan Bende  wrote:
> >
> > > +1 (binding)
> > >
> > > - Ran through release helper and everything checked out
> > > - Verified some test flows with the restricted components + keytab CS
> > >
> > >
> > >
> > > On Fri, Mar 23, 2018 at 2:42 PM, Mark Payne 
> > wrote:
> > > > +1 (binding)
> > > >
> > > > Was able to verify hashes, build with contrib-check, and start up
> > > application. Performed some basic functionality tests and all worked as
> > > expected.
> > > >
> > > > Thanks!
> > > > -Mark
> > > >
> > > >
> > > >> On Mar 23, 2018, at 6:02 AM, Takanobu Asanuma <
> tasan...@yahoo-corp.jp
> > >
> > > wrote:
> > > >>
> > > >> Thanks for all your efforts, Joe.
> > > >>
> > > >> I have one question. The version of the generated package is
> > > nifi-1.7.0-SNAPSHOT. Is this correct at this stage? If it's ok,
> > > +1(non-binding).
> > > >>
> > > >> - Succeeded "mvn -T 2.0C clean install -DskipTests -Prpm"
> > > >> - Started secure cluster mode
> > > >> - Verified sample dataflows work fine
> > > >> - Verified the whitelist feature(NIFI-4761) works fine
> > > >>
> > > >> -Takanobu Asanuma
> > > >>
> > > >> -Original Message-
> > > >> From: Joe Witt [mailto:joew...@apache.org]
> > > >> Sent: Friday, March 23, 2018 1:12 AM
> > > >> To: dev@nifi.apache.org
> > > >> Subject: [VOTE] Release Apache NiFi 1.6.0
> > > >>
> > > >> Hello,
> > > >>
> > > >> I am pleased to be calling this vote for the source release of
> Apache
> > > NiFi nifi-1.6.0.
> > > >>
> > > >> The source zip, including signatures, digests, etc. can be found at:
> > > >> https://repository.apache.org/content/repositories/
> orgapachenifi-1122
> > > >>
> > > >> The Git tag is nifi-1.6.0-RC1
> > > >> The Git commit ID is 49a71f4740c9fac38958961f78dd3cde874b0e45
> > > >> https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> > > 49a71f4740c9fac38958961f78dd3cde874b0e45
> > > >>
> > > >> Checksums of nifi-1.6.0-source-release.zip:
> > > >> SHA1: 4fb82f386a0aa83614cc01449e540527443811ce
> > > >> SHA256: 4df6638ec87a5bee12e7978abc6413
> 7ee5da5fc8c399e34cf34ca1c3720a
> > > c891
> > > >> SHA512: 6fa536f9618c6c153c04df5db59913
> eaf3dd54ae2389368129ac6237f755
> > > 19e1eee7ba0ca70145a95de01517a1c3ea1f36975895d9d72bb04abb56b7934e013a
> > > >>
> > > >> Release artifacts are signed with the following key:
> > > >> https://people.apache.org/keys/committer/joewitt.asc
> > > >>
> > > >> KEYS file available here:
> > > >> https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > >>
> > > >> 135 issues were closed/resolved for this release:
> > > >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12316020&version=12342422
> > > >>
> > > >> Release note highlights can be found here:
> > > >> https://cwiki.apache.org/confluence/display/NIFI/
> > > Release+Notes#ReleaseNotes-Version1.6.0
> > > >>
> > > >> The vote will be open for 72 hours.
> > > >> Please download the release candidate and evaluate the necessary
> items
> > > including checking hashes, signatures, build from source, and test.
> The
> > > please vote:
> > > >>
> > > >> [ ] +1 Release this package as nifi-1.6.0 [ ] +0 no opinion [ ] -1
> Do
> > > not release this package because...
> > > >
> > >
> >
>

Re: NiFi Versioned Process Group Status Icons

[Matt Gilman]

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 encapsulated versioned Process Groups and does not include itself.
Like we have with the status icons for the encapsulated Processors and
Ports. Even if this Process Group is not configured to have any
encapsulated components, we still render the counts as zero.

Additionally, the presence of the icons helps drive awareness of the
feature.

Rob or Drew may have some additional insight to add. Hope this helps

Matt

On Fri, Mar 23, 2018 at 12:10 AM, Peter Wicks (pwicks) 
wrote:

> Why does NiFi show status icons for Versioned Process Group's on servers
> that are not configured to connect to a NiFi Registry?
>
> Thanks,
>   Peter
>

Re: Add interrupt option for stopped processors with active threads

[Matt Gilman]

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 efforts.

Matt

[1] https://github.com/apache/nifi/pull/2555
[2] https://issues.apache.org/jira/browse/NIFI-1295

On Thu, Mar 22, 2018 at 1:37 PM, Karthik Kothareddy (karthikk) [CONT - Type
2]  wrote:

> Hello,
>
> Is there an ETA on the below Improvement? Or is it in the scope for any
> future releases?
>
> https://issues.apache.org/jira/browse/NIFI-78
>
> Thanks
> Karthik
>

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

[Matt Gilman]

+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 9, 2018, 3:10 PM Scott Aslan 
> wrote:
> >>>
> >>> > All,
> >>> >
> >>> > Following a solid discussion for the past couple of weeks [1]
> regarding
> >>> the
> >>> > establishment of Fluid Design System as a sub-project of Apache
> NiFi, I'd
> >>> > like to
> >>> > call a formal vote to record this important community decision and
> >>> > establish consensus.
> >>> >
> >>> > The scope of this project is to define a theme-able set of high
> quality
> >>> UI
> >>> > components and utilities for use across the various Apache NiFi web
> >>> > applications in order to provide a more consistent user experience.
> >>> >
> >>> > I am a +1 and looking forward to the future work in this area.
> >>> >
> >>> > The vote will be open for 72 hours and be a majority rule vote.
> >>> >
> >>> > [ ] +1 Establish Fluid Design System, a subproject of Apache NiFi
> >>> > [ ]   0 Do not care
> >>> > [ ]  -1 Do not establish Fluid Design System, a subproject of Apache
> NiFi
> >>> >
> >>> > Thanks,
> >>> >
> >>> > ScottyA
> >>> >
> >>> > [1] *
> >>> >
> >>> http://mail-archives.apache.org/mod_mbox/nifi-dev/201802.mbox/%
> 3CCAKeSr4ibXX9xzGN1GhdVv5uTmWvfB3QULXF9orzw4FYD0n7taQ%40mail.gmail.com%3E
> >>> > <
> >>> >
> >>> http://mail-archives.apache.org/mod_mbox/nifi-dev/201802.mbox/%
> 3CCAKeSr4ibXX9xzGN1GhdVv5uTmWvfB3QULXF9orzw4FYD0n7taQ%40mail.gmail.com%3E
> >>> > >*
> >>> >
> >>>
>

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

[Matt Gilman]

;> > > changes are already available on the core project i.e NiFi. One
> >> challenge
> >> > > is that the committer of the sub-project should have the
> courtesy to
> >> > check
> >> > > wether the supporting changes are made available to the core
> project
> >> and
> >> > > track its status but given how contributions are being handled
> in
> >> > > nifi-registry project, I don’t think it’s going to be that much
> of a
> >> > > headache.
> >> > >
> >> > > We could also add to the helper doc mentioning that if the
> >> contribution
> >> > is
> >> > > going to affect a core component, the contributor needs to add
> the
> >> JIRA
> >> > id
> >> > > of the core project’s supporting changes in the sub-projects’
> issue
> >> > > description.
> >> > >
> >> > > On Thu, 22 Feb 2018 at 10:42 PM, Matt Gilman <
> matt.c.gil...@gmail.com
> >> >
> >> > > wrote:
> >> > >
> >> > > > Joe, Joe,
> >> > > >
> >> > > > Regarding the release process... I think it could be similar
> to how
> >> > folks
> >> > > > verified and validated the NiFi Registry release. Guidance
> was given
> >> > in a
> >> > > > helper guide regarding how to obtain/build a branch or PR that
> >> > references
> >> > > > the new components. For the Registry release, there was a PR
> for
> >> NiFi
> >> > > that
> >> > > > had the supporting changes already available.
> >> > > >
> >> > > > We may have this issue any time we release new versions that
> depend
> >> on
> >> > > > another (sub)project.
> >> > > >
> >> > > > Matt
> >> > > >
> >> > > > On Thu, Feb 22, 2018 at 11:39 AM, Joe Percivall <
> >> jperciv...@apache.org
> >> > >
> >> > > > wrote:
> >> > > >
> >> > > > > Scott,
> >> > > > >
> >> > > > > Definitely like the direction of standardizing NiFi and
> Registry
> >> > around
> >> > > > the
> >> > > > > same set of components, so the user has a common UX. Is
> there
> >> > precedent
> >> > > > for
> >> > > > > creating a new sub-project just for common
> components/modules to
> >> be
> >> > > used
> >> > > > by
> >> > > > > the top-level, and it's other sub-projects? My concerns are
> >> similar
> >> > to
> >> > > > > Joe's. Along those lines, if the core problems we're trying
> to
> >> > address
> >> > > is
> >> > > > > the release process and distribution, is there a less
> >> "heavy-weight"
> >> > > > > avenue?
> >> > > > >
> >> > > > > In the past, we've also talked about pulling out the core
> NiFi
> >> > > framework
> >> > > > to
> >> > > > > be shared between NiFi and MiNiFi-Java for similar reasons.
> How
> >> we go
> >> > > > about
> >> > > > > solving this for the UI could be used a model for the core
> >> framework
> >> > as
> >> > > > > well.
> >> > > > >
> >> > > > > - Joe
> >> > > > >
> >> > > > > On Thu, Feb 22, 2018 at 10:58 AM, Mike Thomsen <
> >> > mikerthom...@gmail.com
> >> > > >
> >> > > > > wrote:
> >> > > > >
> >> > > > > > Also, what sort of framework is the UI being standardized
> on?
> >> > > Angular?
> >> > > > > > React? Something else?
> >> > > > > >
> >> > > > > > On Thu, Feb 22, 2018 at 10:03 AM, Joe Witt <

Re: Policies for root Process Group.

[Matt Gilman]

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" gives
that user access to get into the UI and to manage users, groups and
policies. But if that user wants to start modifying the flow, they need to
grant themselves policies for the root process group. The system is unable
to do this automatically because in a new flow the UUID of the root process
group is not permanent until the flow.xml.gz is generated. If the NiFi
instance is an upgrade from an existing flow.xml.gz or a 1.x instance going
from unsecure to secure, then the "Initial Admin Identity" user is
automatically given the privileges to modify the flow."

Because of this, when there is no existing flow, granting permissions to
the root group would need to happen after this initial startup.

Matt


On Mon, Feb 26, 2018 at 3:26 PM, Daniel Hernandez <
daniel.hernan...@civitaslearning.com> wrote:

> Hi Matt,
>
> Thanks for your answer.
>
> Do you know if there is a way to preconfigure this value when running
> Nifi's Docker image? I am making the calls from an integration test that
> runs a docker container with the Nifi server. I already check and the value
> under  in the flow.xml.gz file changes everytime I deploy
> the container, I guess it is created at startup.  Is it possible that I can
> change my docker image to get a fix root group value?
>
> Thanks,
>
> Daniel
>
> On Mon, Feb 26, 2018 at 11:35 AM, Daniel Hernandez <
> daniel.hernan...@civitaslearning.com> wrote:
>
> > Hi,
> >
> > I am currently working on calling the Nifi REST API to get the 'root'
> > process group and setting it as parent for a new process-group.
> >
> > However I am getting the next messages:
> >
> > Attempting GET request to: JerseyWebTarget {
> https://127.0.0.1:8443/nifi-
> > api/process-groups/root }
> > 2018-02-26 11:06:55.341 DEBUG  --- [   main]
> > c.c.p.n.c.i.b.BootApiClient  :
> > 2018-02-26 11:06:55.341 DEBUG  --- [   main]
> > c.c.p.n.c.i.b.BootApiClient  : Received 403 response from GET
> > to JerseyWebTarget { https://127.0.0.1:8443/nifi-api/process-groups/root
> }
> >
> > com.civitaslearning.platform.nifi.client.invoker.boot.exception.
> NifiForbiddenException:
> > No applicable policies could be found. Contact the system administrator.
> >
> > This is the content of my authorizations.xml file:
> >
> > 
> >
> > 
> >
> > 
> >
> >  > resource="/flow" action="R">
> >
> > 
> >
> > 
> >
> >  > resource="/restricted-components" action="W">
> >
> > 
> >
> > 
> >
> >  > resource="/tenants" action="R">
> >
> > 
> >
> > 
> >
> >  > resource="/tenants" action="W">
> >
> > 
> >
> > 
> >
> >  > resource="/policies" action="R">
> >
> > 
> >
> > 
> >
> >  > resource="/policies" action="W">
> >
> > 
> >
> > 
> >
> >  > resource="/controller" action="R">
> >
> > 
> >
> > 
> >
> >  > resource="/controller" action="W">
> >
> > 
> >
> > 
> >
> >  > resource="/process-groups/root" action="R">
> >
> > 
> >
> > 
> >
> >  > resource="/process-groups/root" action="W">
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> > And this is the content of authorizations.xml
> >
> > 
> >
> > 
> >
> > file-access-policy-provider
> >
> > org.apache.nifi.authorization.FileAccessPolicyProvider > class>
> >
> > file-user-group-
> > provider
> >
> > ./conf/authorizations.
> > xml
> >
> > CN=civitas,
> > OU=ApacheNifi
> >
> > 
> >
> >
> > 
> >
> > 
> >
> > 
> >
> > managed-authorizer
> >
> > org.apache.nifi.authorization.StandardManagedAuthorizer > class>
> >
> > file-access-policy-
> > provider
> >
> > 
> >
> > 
> >
> >
> > And users.xml
> >
> >
> > 
> >
> > 
> >
> > 
> >
> > 
> >
> >  > identity="CN=civitas, OU=ApacheNifi"/>
> >
> > 
> >
> > 
> >
> > I already create a policy using the same user cert so I guess the DN is
> > valid.
> > Am I defining the policy or making the call in a wrong way?
> >
> > Thanks in advance,
> >
> > Daniel Hernandez
> >
> >
> >
>

Re: Policies for root Process Group.

[Matt Gilman]

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 these policies manually after starting up. You can see these
endpoints in action if you open your browser's Developer Tools and you
perform these actions in the UI. You should be able to update your client
following these examples.

Matt

On Mon, Feb 26, 2018 at 11:35 AM, Daniel Hernandez <
daniel.hernan...@civitaslearning.com> wrote:

> Hi,
>
> I am currently working on calling the Nifi REST API to get the 'root'
> process group and setting it as parent for a new process-group.
>
> However I am getting the next messages:
>
> Attempting GET request to: JerseyWebTarget {
> https://127.0.0.1:8443/nifi-api/process-groups/root }
> 2018-02-26 11:06:55.341 DEBUG  --- [   main]
> c.c.p.n.c.i.b.BootApiClient  :
> 2018-02-26 11:06:55.341 DEBUG  --- [   main]
> c.c.p.n.c.i.b.BootApiClient  : Received 403 response from GET
> to JerseyWebTarget { https://127.0.0.1:8443/nifi-api/process-groups/root }
>
> com.civitaslearning.platform.nifi.client.invoker.boot.exception.
> NifiForbiddenException:
> No applicable policies could be found. Contact the system administrator.
>
> This is the content of my authorizations.xml file:
>
> 
>
> 
>
> 
>
>  resource="/flow" action="R">
>
> 
>
> 
>
>  resource="/restricted-components" action="W">
>
> 
>
> 
>
>  resource="/tenants" action="R">
>
> 
>
> 
>
>  resource="/tenants" action="W">
>
> 
>
> 
>
>  resource="/policies" action="R">
>
> 
>
> 
>
>  resource="/policies" action="W">
>
> 
>
> 
>
>  resource="/controller" action="R">
>
> 
>
> 
>
>  resource="/controller" action="W">
>
> 
>
> 
>
>  resource="/process-groups/root" action="R">
>
> 
>
> 
>
>  resource="/process-groups/root" action="W">
>
> 
>
> 
>
> 
>
> 
>
> And this is the content of authorizations.xml
>
> 
>
> 
>
> file-access-policy-provider
>
>
> org.apache.nifi.authorization.FileAccessPolicyProvider
>
> file-user-group-provider
>
> ./conf/authorizations.xml
>
> CN=civitas,
> OU=ApacheNifi
>
> 
>
>
> 
>
> 
>
> 
>
> managed-authorizer
>
>
> org.apache.nifi.authorization.StandardManagedAuthorizer
>
> file-access-policy-provider
>
> 
>
> 
>
>
> And users.xml
>
>
> 
>
> 
>
> 
>
> 
>
>  identity="CN=civitas, OU=ApacheNifi"/>
>
> 
>
> 
>
> I already create a policy using the same user cert so I guess the DN is
> valid.
> Am I defining the policy or making the call in a wrong way?
>
> Thanks in advance,
>
> Daniel Hernandez
>

Re: Create custom content viewer

[Matt Gilman]

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/tree/master/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-content-viewer

On Sun, Feb 25, 2018 at 12:13 AM, Дмитрий Круглов <
dimpalych...@mail.ru.invalid> wrote:

>
> Is it possible to create custom content viewer, to extend functionality,
> or i have to append some code to exist standart comtent viewer and
> recompile?
> --
> Отправлено из Mail.Ru для Android

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

[Matt Gilman]

Joe, Joe,

Regarding the release process... I think it could be similar to how folks
verified and validated the NiFi Registry release. Guidance was given in a
helper guide regarding how to obtain/build a branch or PR that references
the new components. For the Registry release, there was a PR for NiFi that
had the supporting changes already available.

We may have this issue any time we release new versions that depend on
another (sub)project.

Matt

On Thu, Feb 22, 2018 at 11:39 AM, Joe Percivall 
wrote:

> Scott,
>
> Definitely like the direction of standardizing NiFi and Registry around the
> same set of components, so the user has a common UX. Is there precedent for
> creating a new sub-project just for common components/modules to be used by
> the top-level, and it's other sub-projects? My concerns are similar to
> Joe's. Along those lines, if the core problems we're trying to address is
> the release process and distribution, is there a less "heavy-weight"
> avenue?
>
> In the past, we've also talked about pulling out the core NiFi framework to
> be shared between NiFi and MiNiFi-Java for similar reasons. How we go about
> solving this for the UI could be used a model for the core framework as
> well.
>
> - Joe
>
> On Thu, Feb 22, 2018 at 10:58 AM, Mike Thomsen 
> wrote:
>
> > Also, what sort of framework is the UI being standardized on? Angular?
> > React? Something else?
> >
> > On Thu, Feb 22, 2018 at 10:03 AM, Joe Witt  wrote:
> >
> > > Scott
> > >
> > > Ok so extract out the fluid design work you started with NiFi Registry
> > > to its own codebase which can be rev'd and published to NPM making it
> > > easier to consume/reuse across NiFi projects and offers better
> > > consistency.  This sounds interesting.
> > >
> > > In thinking through the additional community effort or the effort
> > > trade-off:
> > > How often do you anticipate we'd be doing releases (and thus
> > > validation/voting) for this?
> > > How often would those differ from when we'd want to do a NiFi or NiFi
> > > Registry release?
> > > How do you envision the community would be able to help vet/validate
> > > releases of these modules?
> > >
> > > Thanks
> > > Joe
> > >
> > > On Thu, Feb 22, 2018 at 8:18 AM, Scott Aslan 
> > > wrote:
> > > > NiFi Community,
> > > >
> > > > I'd like to initiate a discussion around creating a sub-project of
> NiFi
> > > to
> > > > encompass the Fluid Design System NgModule created during the
> > development
> > > > of the NiFi Registry. A possible name for this sub-project is simply
> > > > "NiFi Fluid
> > > > Design System". The idea would be to create a sub-project that
> > > distributes
> > > > an atomic set of high quality, reuse-able, theme-able, and testable
> > UI/UX
> > > > components, fonts, and other JS modules for use across the various
> web
> > > > applications throughout the NiFi universe (uNiFiverse???). Both NiFi
> > and
> > > > NiFi Registry web applications would eventually leverage this module
> > via
> > > > npm. This approach will enable us to provide our users with a
> > consistent
> > > > experience across web applications. Creating a sub-project would also
> > > allow
> > > > the FDS code to evolve independently of NiFi/NiFi registry and be
> > > released
> > > > on it's own timeline. In addition, it would make tracking issues/work
> > > much
> > > > clearer through a separate JIRA.
> > > >
> > > > Please discuss and provide and thoughts or feedback.
> > > >
> > > > Thanks,
> > > >
> > > > Scotty
> > >
> >
>
>
>
> --
> *Joe Percivall*
> linkedin.com/in/Percivall
> e: jperciv...@apache.com
>

Re: Double click for failure queues

[Matt Gilman]

Double-clicking on the connection label should open the connection
configuration dialog. Double-clicking on the actual path will generate a
bend point. The connection label can then be attached to any bend point.

Matt

On Thu, Feb 1, 2018 at 2:02 PM, Karthik Kothareddy (karthikk) [CONT - Type
2]  wrote:

> All,
>
> I am using 1.4.0 and I see that double-click to configure (for both queues
> and processors) feature as very useful and intuitive to use. However, if I
> double click on a queue which has a failure relationship it doesn't work as
> expected and I have to right-click to configure it. Is this by design? Or a
> bug in UI?
>
> Just curious...
>
> Thanks
> Karthik
>

Re: Incorrect return classes specified on api annotations

[Matt Gilman]

Thanks for reaching out Charlie. If you wanted to submit a PR for this, I
would be happy to review/merge it for you.

Matt

On Wed, Jan 31, 2018 at 5:34 PM, Charlie Meyer <
charlie.me...@civitaslearning.com> wrote:

> Hi,
>
> I opened up https://issues.apache.org/jira/browse/NIFI-4835 earlier today
> for a few places where the return type class did not reflect the entity
> that is being returned. For now, I've locally patched my build and was able
> to regenerate a correct swagger json, but figured id bring it up here as
> well so it can hopefully make it into the next release.
>
> Thanks!
>

Re: Help & advice needed on application.js in Processors

[Matt Gilman]

Just wanted to add that the Custom UI's are displayed in an iframe.
Sometimes the hard reload does not trigger the iframe to reload. You may
need to open that frame source in a new tab and do a hard reload.

Also, can you confirm that you've updated your
META-INF/nifi-processor-configuration accordingly?

Matt

On Tue, Jan 30, 2018 at 9:07 PM, Koji Kawamura 
wrote:

> Hi Dave,
>
> If you can confirm the updated application.js is included in the war
> file, then it sounds like a matter of Web browser caching. The old
> application.js cached at the client Web browser may be used. A hard
> reload (Ctrl + Shift + R for Chrome) may help if that's the case.
>
> Thanks,
> Koji
>
> On Wed, Jan 31, 2018 at 6:48 AM, DAVID SMITH 
> wrote:
> > Hi
> > I am trying to create a processor that is partially based on the
> UpdateAttribute processor 0.7.3.I have cloned the UpdateAttribute source,
> renamed the processor and I have started by trying to amend the Advanced
> configuration UI. I have found that I can change labels for fields in the
> Advanced configuration UI in WEB-INF/jsp/worksheet.jsp, and these are
> reflected in the Advanced UI after a reload.
> > However any changes that I make in webapp/js/application.js, such as
> changing the label on the Rule FIlter button never gets picked up and
> displayed in the UI.I have unpacked the war file and the application.js
> looks exactly as I have edited it.
> > When I build the new processor  nar I am using mvn clean install, I am
> seeing no errors, also when NiFi loads there are no errors or warnings.Is
> there a developers guide for creating this type of UI in processors, or can
> someone help and tell me why my changes are not being picked up?
> > Many thanksDave
>

Re: [VOTE] Release Apache NiFi MiNiFi C++ 0.4.0 RC1

[Matt Gilman]

+1 (binding) Release this package as nifi-minifi-cpp-0.4.0

Verified hashes, signatures, build, etc. Ran some samples flows integrating
with a local NiFi instance.

Looks good guys. Aldrin, thanks for RMing!

Matt

On Thu, Jan 25, 2018 at 4:17 PM, Aldrin Piri  wrote:

> Hey Andy,
>
> Thanks for reporting and the patch.  The files highlighted definitely
> seemed to leak into the source distribution but are not necessarily
> dealbreakers from the release perspective.  Saying the rest the vote
> successfully releases, I can include a note on our download page as Kevin
> highlighted to note removing these files if there are any issues in
> building.
>
> For anyone else that verifies, should you run into issues, I would
> encourage you to try manually removing the files listed and please let us
> know the OS and flex version so we can enumerate these in documentation.
> Thanks!
>
> On Thu, Jan 25, 2018 at 4:03 PM, Kevin Doran  wrote:
>
> > +1 (non-binding)
> >
> > Ran through the steps in the Release Helper Guide on Mac OS 10.12.6 using
> > the source tar without issue.
> >
> > I'm ok with documenting the issue Andy C found on the source tarball
> > download page as Marc P suggested.
> >
> > Thanks everyone!
> > Kevin
> >
> > On 1/24/18, 01:36, "Aldrin Piri"  wrote:
> >
> > Hello Apache NiFi Community,
> >
> > I am pleased to call this vote for the source release of Apache NiFi
> > MiNiFi
> > C++, nifi-minifi-cpp-0.4.0.
> >
> > The source archive, signature, and digests can be located at:
> >
> > Source Archive:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.4.0/nifi-minifi-cpp-0.4.0-source.tar.gz
> >
> > GPG armored signature:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.4.0/nifi-minifi-cpp-0.4.0-source.tar.gz.asc
> >
> > Source MD5:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.4.0/nifi-minifi-cpp-0.4.0-source.tar.gz.md5
> >
> > Source SHA1:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.4.0/nifi-minifi-cpp-0.4.0-source.tar.gz.sha1
> >
> > Source SHA256:
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/
> > 0.4.0/nifi-minifi-cpp-0.4.0-source.tar.gz.sha256
> >
> > The Git tag is minifi-cpp-0.4.0-RC1
> > The Git commit hash is c05d467758c861f38a00c6ac5f64f75d6ca0ce05
> > * https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.
> > git;a=commit;h=c05d467758c861f38a00c6ac5f64f75d6ca0ce05
> > * https://github.com/apache/nifi-minifi-cpp/commit/
> > c05d467758c861f38a00c6ac5f64f75d6ca0ce05
> >
> > Checksums of nifi-minifi-cpp-0.4.0-source.tar.gz:
> > MD5: 27d82a635cee3f97841eb6af01248712
> > SHA1: 3b8bb029bcca64897223f7fb27122ac9642cd92b
> > SHA256: 887879d65514ccc7ee598ba650d05f7ff56145d8462707d38b137363ea97
> > 1965
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/aldrin
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/dev/nifi/KEYS
> >
> > 49 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12321520&version=12341641
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/MINIFI/
> > Release+Notes#ReleaseNotes-Versioncpp-0.4.0
> >
> > The vote will close 27 January at 12PM EST [1].
> >
> > Please download the release candidate and evaluate the necessary
> items
> > including checking hashes, signatures, build from source, and test.
> > Then
> > please vote:
> >
> > [ ] +1 Release this package as nifi-minifi-cpp-0.4.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks!
> >
> >
> > [1] You can determine this time for your local time zone at
> > https://s.apache.org/minifi-cpp-0.4.0-rc1-close
> >
> >
> >
> >
>

Re: Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project nifi-poi-processors: Too many files with unapproved license

[Matt Gilman]

Are you possibly running your build with multiple threads? There have been
issues in the past running multi-threaded builds with the contrib-check
profile enabled.

Matt

On Tue, Jan 23, 2018 at 12:26 PM, Sivaprasanna 
wrote:

> When I tried to build the master branch, the build fails here. When I took
> a look at the
> ~nifi\nifi-nar-bundles\nifi-poi-bundle\nifi-poi-processors\target\rat.txt,
> it had the following content:
>
> 
>
>
> *
> Summary
> ---
> Generated at: 2018-01-23T22:43:53+05:30
> Notes: 0
> Binaries: 4
> Archives: 0
> Standards: 7
>
> Apache Licensed: 6
> Generated Documents: 0
>
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
>
> 1 Unknown Licenses
>
> ***
>
> Unapproved licenses:
>
>
> E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/src/test/resources/Unsupported.xls
>
> ***
>
> Archives:
>
> *
>   Files with Apache License headers will be marked AL
>   Binary files (which do not require AL headers) will be marked B
>   Compressed archives will be marked A
>   Notices, licenses etc will be marked N
>   AL
> E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/pom.xml
>   AL
> E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/src/main/java/org/apache/nifi/processors/poi/
> ConvertExcelToCSVProcessor.java
>   AL
> E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/src/main/resources/docs/org.apache.nifi.processors.poi.
> ConvertExcelToCSVProcessor/additionalDetails.html
>   AL
> E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/src/main/resources/META-INF/services/
> org.apache.nifi.processor.Processor
>   AL
> E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/src/test/java/org/apache/nifi/processors/poi/
> ConvertExcelToCSVProcessorTest.java
>   B
>  E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/src/test/resources/CollegeScorecard.xlsx
>   B
>  E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/src/test/resources/dataformatting.xlsx
>   AL
> E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/src/test/resources/logback-test.xml
>   B
>  E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/src/test/resources/TwoSheets.xlsx
>  !?
> E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/src/test/resources/Unsupported.xls
>   B
>  E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/src/test/resources/with-blank-cells.xlsx
>
> *
>  Printing headers for files without AL header...
>
>
> ===
> ==E:/Workspace/nifi/nifi-nar-bundles/nifi-poi-bundle/nifi-
> poi-processors/src/test/resources/Unsupported.xls
> ===
> ÐÏ?ࡱ?á>???þÿ
> ?1???þÿÿÿþÿÿÿ0???
> 
> 
> 
> 
> 
> 
> 
> ???£DÍ?Á???á???°?Á?â???\?pjames
>
>
> B???°?a?À???=?œ???¯?¼?=?
> ??­R“!8???X?@???"???·?Ú?1???
> Ü???C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?
> r?i?1???Ü???C?a?l?i?b?r?i?1???Ü???C?
> a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?1?*?h???6?
> ?C?a?l?i?b?r?i?
> ?L?i?g?h?t?1???,???6?¼?C?a?l?i?b?r?i?1???6?¼
> ?C?a?l?i?b?r?i?1???Ü???6?¼?C?a?l?i?b?r?i?1???Ü??
> ?C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?
> i?1???Ü??C?a?
> l?i?b?r?i?1???Ü?¼?C?a?l?i?b?r?i?1???Ü???4?¼?
> C?a?l?i?b?r?i?1???Ü???4???C?a?l?i?b?r?i?1???Ü???
> ?¼?C?a?l?i?b?r?i?1???Ü???
> ???C?a?l?i?b?r?i?1???Ü???C?a?l?i?b?r?i?
> 1???Ü?¼?C?a?l?i?b?r?i?1???Ü???
> ???C?a?l?i?b?r?i??"$"#,##0_);\("$"#,##0\)??!
> ??"$"#,##0_);[Red]\("$"#,##0\)??"??"$"#,##0.00_);\("
> $"#,##0.00\)??'???"??"$"#,##0.00_);[Red]\("$"#,##0.00\)??7?*?2??_("$"*
> #,##0_);_("$"* \(#,##0\);_("$"* "-"_);_(@_)??.?)?)??_(* #,##0_);_(*
> \(#,##0\);_(* "-"_);_(@_),?:??_("$"* #,##0.00_);_("$"*
> \(#,##0.00\);_("$"* "-"??_);_(@_)??6?+?1??_(* #,##0.00_);_(*
> \(#,##0.00\);_(* "-"??_);_(@_)à???

Re: [VOTE] Release Apache NiFi MiNiFi 0.4.0 RC2

[Matt Gilman]

+1 Release this package as minifi-0.4.0

Verified hashes, signature, build, etc. Ran sample flows and everything
looks good.

Thanks for RMing Aldrin!

Matt

On Fri, Jan 19, 2018 at 3:24 AM, Koji Kawamura 
wrote:

> Verified the hash, built on Windows Server 2016, Java 1.8.0_144
> successfully.
> Confirmed that the basic template transform capability with NiFi 1.5.0
> including RemoteProcessGroup.
> The getting-started example flow, tailing a file at MiNiFi (0.4.0 RC2)
> and sending it via S2S to NiFi (1.5.0) worked as expected.
> https://nifi.apache.org/minifi/getting-started.html
> Confirmed that the config.yml created by the toolkit has the correct
> ID for the input port.
>
> +1 (binding) Release this package as minifi-0.4.0
>
> On Fri, Jan 19, 2018 at 5:55 AM, Aldrin Piri  wrote:
> > Hello,
> >
> > I am pleased to call this vote for the source release of Apache NiFi
> MiNiFi nifi-minifi-0.4.0.
> >
> > The source zip, including signatures, digests, etc. can be found at:
> > https://repository.apache.org/content/repositories/orgapachenifi-1119
> >
> > The Git tag is nifi-minifi-0.4.0-RC2
> > The Git commit ID is 5e19068e2d35dd9b5d5f45e75efb0414d84d226b
> > https://git-wip-us.apache.org/repos/asf?p=nifi-minifi.git;a=commit;h=
> 5e19068e2d35dd9b5d5f45e75efb0414d84d226b
> > https://github.com/apache/nifi-minifi/commit/
> 5e19068e2d35dd9b5d5f45e75efb0414d84d226b
> >
> > Checksums of nifi-minifi-0.4.0-source-release.zip:
> > MD5: 237bb2f3fe26ff6451273c3c39579bf6
> > SHA1: 2d53dd08b55a2799da97008bf971657546c0a752
> > SHA256: b0ee425f7c214d423f22b75aa2006dcdabf407cd29b0bd2c4f8a8ea3a3ec4b18
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/aldrin.asc
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > 5 issues were closed/resolved for this release:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12319921&version=12342439
> >
> > Release note highlights can be found here:
> > https://cwiki.apache.org/confluence/display/MINIFI/
> Release+Notes#ReleaseNotes-Version0.4.0
> >
> > The vote will be open until 4:00PM EST, 22 January 2018 [1].
> >
> > Please download the release candidate and evaluate the necessary items
> including checking hashes, signatures, build
> > from source, and test.  Then please vote:
> >
> > [ ] +1 Release this package as minifi-0.4.0
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks!
> >
> > [1] You can determine this time for your local time zone at
> https://s.apache.org/minifi-0.4.0-rc2-close
>

Re: how to declare dependency?

[Matt Gilman]

Mar,

By using a dependency like that (without the version), it must be declared
in dependencyManagement someplace. If the jar isn't being pulled into the
resulting artifact it's likely because the dependency has a scope of
provided. You can override that scope to compile when you reference it.

Matt

On Fri, Jan 12, 2018 at 8:34 AM, Martin Mucha  wrote:

> Hi,
>
> in nifi-standard-processors there is this dependency
>
> 
> org.apache.nifi
> nifi-record
> 
>
> if I just copy paste into our project some class from this bundle (to fix
> bugs) and add dependencies as mentioned one, it builds. However nifi wont
> start, because nifi-record related classes are not on classpath.
>
> What shall I do to get them on classpath? For nifi-standard-processors it's
> fine to have nifi-record as provided, but apparently for our project,
> extending the same parent, it's not. nifi-record is not provided or part of
> built nar. How to fix this?
>
> thanks,
> Mar.
>

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

[Matt Gilman]

+1 (binding) Release this package as nifi-1.5.0

Verified signature, hashes, build, etc. Ran through a number of scenarios
with Apache NiFi Registry 0.1.0 and everything is working as expected.

Thanks Joe for RMing this release!

Matt

On Wed, Jan 10, 2018 at 2:22 PM, Rob Moran  wrote:

> +1, non-binding
>
> * All looks good/in place following the release helper
> * Reviewed help docs related to new Registry integration
> * Connected a registry client and did some quick testing of basic version
> control related actions
>
>
> On Wed, Jan 10, 2018 at 1:24 PM Andrew Lim 
> wrote:
>
> > +1 (non-binding)
> >
> > -Ran full clean install on OS X (10.11.6)
> > -Tested integration with NiFi Registry
> > -Ran record reader/writer flows
> > -Reviewed resolved “Core UI” component Jiras and spot checked inclusion
> in
> > build
> > -Reviewed documentation
> >
> > Drew
> >
> >
> > > On Jan 9, 2018, at 5:19 AM, Joe Witt  wrote:
> > >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi nifi-1.5.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1116
> > >
> > > The Git tag is nifi-1.5.0-RC1
> > > The Git commit ID is 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed
> > >
> > https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=
> 46d30c7e92f0ad034d9b35bf1d05c350ab5547ed
> > >
> > > Checksums of nifi-1.5.0-source-release.zip:
> > > MD5: 046f2dde4af592dd8c05e55c2bbb3c4f
> > > SHA1: 63b9a68b9f89200fd31f5561956a15b45b1b9c8c
> > > SHA256: 40b155c4911414907835f2eb0d5a4da798935f27f1e5134218d904fe6c94
> 2d13
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/joewitt.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 195 issues were closed/resolved for this release:
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12316020&version=12341668
> > >
> > > Release note highlights can be found here:
> > >
> > https://cwiki.apache.org/confluence/display/NIFI/
> Release+Notes#ReleaseNotes-Version1.5.0
> > >
> > > The vote will be open for 72 hours.
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build
> > > from source, and test.  The please vote:
> > >
> > > [ ] +1 Release this package as nifi-1.5.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> >
> >
>
> --
> Rob
>

Re: [VOTE] Release Apache NiFi Registry 0.1.0

[Matt Gilman]

+1 (binding)

- build, hashes, etc look good
- set up a secure registry and nifi instance and everything worked as
expected

This is a very exciting release. Thanks Bryan for handling the release
manager duties and everyone who contributed!

Matt


On Sun, Dec 31, 2017 at 2:02 PM, Scott Aslan  wrote:

> +1 (binding), Ran through the release helper. verified hashed, LICENSE,
> NOTICE, and README.
>
> Tests
> - setup kerberos based secure reg setup/test with Nifi
> - attempted to reproduce the npm issue, all looks well (Aldrin, I am
> curious as to what caused npm to fail? any other info? maybe some other
> software installed on your machine is causing conflicts?)
>
>
> On Sat, Dec 30, 2017 at 6:16 PM, James Wing  wrote:
>
> > +1 (binding).  Ran through the release helper, verified hashes, LICENSE,
> > NOTICE, and README.  Built the source and performed light testing of the
> > resulting binary.
> >
> > On Thu, Dec 28, 2017 at 10:09 AM, Bryan Bende  wrote:
> >
> > > Hello,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi Registry 0.1.0.
> > >
> > > The source zip, including signatures, digests, etc. can be found at:
> > > https://repository.apache.org/content/repositories/orgapachenifi-1115/
> > >
> > > The Git tag is nifi-registry-0.1.0-RC1
> > > The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca
> > > https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;
> a=commit;h=
> > > 81b99e7b04491eabb72ddf30754053ca12d0fcca
> > >
> > > Checksums of nifi-registry-0.1.0-source-release.zip:
> > > MD5: 56244c3c296cdc9c3fcc6d22590b80d1
> > > SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca
> > > SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95ef
> d301
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/bbende.asc
> > >
> > > KEYS file available here:
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > 65 issues were closed/resolved for this release:
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12320920&version=12340217
> > >
> > > Release note highlights can be found here:
> > > https://cwiki.apache.org/confluence/display/NIFI/
> > > Release+Notes#ReleaseNotes-NiFiRegistry0.1.0
> > >
> > > The vote will be open for 96 hours.
> > >
> > > Please download the release candidate and evaluate the necessary items
> > > including checking hashes, signatures, build from source, and test.
> > >
> > > The please vote:
> > >
> > > [ ] +1 Release this package as nifi-registry-0.1.0
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because...
> > >
> >
>

Re: [ANNOUNCE] New NiFi PMC member Jeff Storck

[Matt Gilman]

Congrats Jeff!

On Tue, Dec 5, 2017 at 12:14 PM, Kevin Doran 
wrote:

> Congrats, Jeff!
>
> On 12/5/17, 11:49, "Tony Kurc"  wrote:
>
> NiFi community,
> On behalf of the Apache NiFi PMC, I am pleased to announce that Jeff
> Storck
> has accepted the PMC's invitation to join the Apache NiFi PMC.  We
> greatly
> appreciate all of Jeff's hard work and generous contributions to the
> project. We look forward to continued involvement in the project.
>
> For those of you enjoying NiFi 1.4.0 release, Jeff was the release
> manager,
> which is a huge complicated set of work. He's also been a long time
> contributor, committer, and a strong member of the community.
>
> Congratulations and welcome, Jeff!
>
> Tony
>
>
>
>

Re: Adding user in NIFI-1.4.0

[Matt Gilman]

Pallavi,

Please refer to our admin guide for instructions on configuring users,
group, and policies [1].

Thanks

Matt

[1]
https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#config-users-access-policies


On Fri, Dec 1, 2017 at 5:53 AM, Bhosale, Pallavi <
pallavi.bhos...@capgemini.com> wrote:

> Hi,
> how to create users in nifi 1.4.0 ??
> need help.
>
> Thanks,
> Pallavi Bhosale
> This message contains information that may be privileged or confidential
> and is the property of the Capgemini Group. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain, copy, disseminate, distribute,
> or use this message or any part thereof. If you receive this message in
> error, please notify the sender immediately and delete all copies of this
> message.
>

Re: Adding Custom UI Components

[Matt Gilman]

The only supported front end extension points are for custom processor UIs
and data viewers (for viewing content of a flowfile in a queue or content
associated with a provenance event). Typically, when front-end capabilities
are added, a JIRA is filed so that some of UX focused community members can
offer suggestions. Because of this, there are no generic means for adding
stuff to the UI. What sort of functionality are you looking to add?

Matt

On Mon, Nov 6, 2017 at 8:14 AM, Alex Aversa  wrote:

> Hello,
>
> I am trying to determine the best practice to inject my own custom UI
> components to the main NiFi user interface (not just custom processor
> UI's)  without having to modify the Apache Nifi code base. I was hoping
> there was a property available in the nifi.properties file that could point
> to a directory containing a custom package.json and corresponding component
> files that would allow front end developers to inject their custom web
> components into the main NiFi user interface. Is this something that is
> supported, or is there a better practice available to address adding custom
> components into main user interface aside from having to fork the code
> base? My thanks in advance for any information you can provide.
>
> Take care,
>
> Alex
>

Re: NiFi Front End Development

[Matt Gilman]

Alex,

That profile is what allows the sources to not be minified or aggregated.
Once NiFi is started, those front-end resources are deployed to

/work/jetty/nifi-web-ui-1.5.0-SNAPSHOT.war/webapp

If your making changes within the NiFi codebase, you can rebuild the
nifi-web-ui module and then nifi-framework-nar (which has a dependency on
nifi-web-ui). Once the resulting framework nar is copied into your
/lib directory you can restart NiFi to realize your changes.

Hope this helps

Matt

On Wed, Nov 1, 2017 at 9:06 AM, Alex Aversa  wrote:

> Ok - Found the setting in the *nifi-web-ui > pom.xml* that prevents the
> aggregation of the front end files. All I needed to do was deactivate
> the "*minify
> and compress*" profile:
>
>
> **
>
> *  minify and compress*
>
> * *
>
> *  false*
> * *
>
> ...and the project structure stays intact when installed on the Jetty
> container allowing me to make updates real-time. If anyone has any other
> sources that have recommendations/best practices for the developer setup
> when working with the front end, it would be a huge help as I didn't see
> much documentation out there.
>
> Thanks,
>
> --alex
>
>
>
>
> On Wed, Nov 1, 2017 at 8:20 AM, Alex Aversa  wrote:
>
> > Hello,
> >
> > I am interested in doing some front-end work on Apache Nifi. I am
> > currently trying to figure out the best practice to setup the project
> such
> > that I can change the front end files (*.css, *.js,  etc) in the
> > nifi-web-ui component and have them sync in the Jetty web container in
> near
> > real time. Currently, I've have been forced run the "package" maven build
> > in the nifi-web-ui component and that is requiring me to wait
> approximately
> > 20 seconds while it re-packages all the front-end files prior to copying
> > them out to the Jetty container and be able to view my changes. It
> appears
> > the "package" step is aggregating multiple source files into  common
> files
> > with a custom naming convention, preventing any simple direct copy of
> these
> > static files from the project into the Jetty container when working on
> the
> > UI. I wanted to know if anyone is aware of a setting I can tweak in the
> > project that makes the project go to a "development" mode where it skips
> > the source file aggregation and renaming step prior to generating the war
> > file for the Jetty container and ultimately keeps the nifi-web-ui
> maintains
> > the same source structure in the web container? If anyone has any
> > insight/guidance on if this is possible, it would be a huge help on this
> > end. Waiting 20 seconds to view minor changes to static files is an
> > exercise in frustration I'd like to avoid. My maven is rusty at best, so
> > the solution didn't seem very apparent to me when I looked at the *.pom
> > files. Many thanks in advance for any assistance you can render.
> >
> > Take care,
> >
> > --Alex
> >
> >
> >
>

Re: Did 1.4.0 introduce a "breaking change" ?

[Matt Gilman]

Andre,

Based on the error, it looks like you've retained your existing
authorizers.xml but upgraded the nifi.security.user.authorizer property in
your nifi.properties. These two are related. The authorizers.xml
file defines the available Authorizers (and now UserGroupProviders and
AccessPolicyProviders). The nifi.security.user.authorizer property in
nifi.properties defines which authorizer to use (via the identifier) from
the authorizers.xml file. If you want to retain your existing
authorizers.xml you'll want to keep that property unchanged as well.

I'll add a note in the migration guide to make sure this is clear.

Thanks

Matt

On Tue, Oct 31, 2017 at 12:05 AM, Andre  wrote:

> Matt,
>
> I did some investigation and it seems like if you simply copy the old
> authorizers.xml into the new setup NiFi fails with
>
> ERROR [main] o.s.web.context.ContextLoader Context initialization failed
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'niFiWebApiSecurityConfiguration': Injection of autowired
> dependencies failed; nested exception is
> org.springframework.beans.factory.BeanCreationException: Could not
> autowire
> method: public void
> org.apache.nifi.web.NiFiWebApiSecurityConfiguration.
> setOtpAuthenticationProvider(org.apache.nifi.web.security.
> otp.OtpAuthenticationProvider);
> nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'otpAuthenticationProvider' defined in class path resource
> [nifi-web-security-context.xml]: Cannot resolve reference to bean
> 'authorizer' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating
> bean with name 'authorizer': FactoryBean threw exception on object
> creation; nested exception is java.lang.Exception: The specified authorizer
> 'managed-authorizer' could not be found.
>
> And similar errors for JWT as well.
>
> Given that populating the new authorizers.xml with the  element
> from the old authorizers.xml seems to solve the issue, seems to me like we
> expect the file to contain references to the new authorizers syntax
> despite using the legacy syntax?
>
> Doesn't seem to be a show stopper but I reckon we should document it.
>
> Cheers
>
>
>
> On Tue, Oct 31, 2017 at 1:43 PM, Matt Gilman 
> wrote:
>
> > Andre,
> >
> > While 1.4.0 introduces a more granular authorizers configuration, the
> > existing 1.3.0 configurations should still be valid. What was breaking
> for
> > you?
> >
> > Matt
> >
> > Sent from my iPhone
> >
> > > On Oct 30, 2017, at 10:24 PM, Andre  wrote:
> > >
> > > Folks,
> > >
> > > I was looking at the upgrade process from 1.3.x to 1.4.0 and it seems
> to
> > me
> > > we introduced a breaking change around the authorizations?
> > >
> > > When I look at the 1.4.0 authorizers.xml and its version 1.3.0 there's
> a
> > > massive discrepancy on the XML tree and the existing 1.3.x version does
> > not
> > > seem to work out of the box on 1.4.0 ?
> > >
> > > Looking at the docs I couldn't find evidence of the migration being
> fully
> > > documented? I suspect users may be able to find their way by adjusting
> > the
> > > instructions for the 0.x upgrade, but shouldn't we have clear
> > instructions
> > > on the upgrade from 1.3.x to 1.4.0?
> > >
> > > Cheers
> >
>

Re: Did 1.4.0 introduce a "breaking change" ?

[Matt Gilman]

Andre,

While 1.4.0 introduces a more granular authorizers configuration, the existing 
1.3.0 configurations should still be valid. What was breaking for you?

Matt

Sent from my iPhone

> On Oct 30, 2017, at 10:24 PM, Andre  wrote:
> 
> Folks,
> 
> I was looking at the upgrade process from 1.3.x to 1.4.0 and it seems to me
> we introduced a breaking change around the authorizations?
> 
> When I look at the 1.4.0 authorizers.xml and its version 1.3.0 there's a
> massive discrepancy on the XML tree and the existing 1.3.x version does not
> seem to work out of the box on 1.4.0 ?
> 
> Looking at the docs I couldn't find evidence of the migration being fully
> documented? I suspect users may be able to find their way by adjusting the
> instructions for the 0.x upgrade, but shouldn't we have clear instructions
> on the upgrade from 1.3.x to 1.4.0?
> 
> Cheers

Re: Initial Admin Identity can't query provenance?

[Matt Gilman]

Peter,

That was by design. The permissions that are granted were primarily driven
by the existing roles in the 0.x baseline. Provenance permissions were
something that was granted in addition to other roles. However, I do see
that whenever there is an existing flow.xml.gz the initial admin is also
given permission the root Process Group and the data in the root Process
Group. This deviates slightly from the 0.x guidance and I could definitely
see granting the ability to query provenance in this case too. Feel free to
file JIRA for this improvement.

Thanks

Matt

On Wed, Oct 25, 2017 at 10:01 PM, Peter Wicks (pwicks) 
wrote:

> I just setup a new NiFi instance and setup myself as the Initial Admin
> Identity, I'm currently the only user on the box and I've made no security
> changes. I noticed today that I couldn't query provenance.
>
> I had to go in and create a new policy and add myself to it. This seems
> odd for an initial admin identity, but maybe it's by design?
>
> Thanks,
>   Peter
>

Re: Troubleshooting Apache NiFi 1.4.0 Authorizations

[Matt Gilman]

Thanks for replying back. Can you ensure your browser cache is cleared? If
that's not it, it's possible your running an older version of Chrome that
is incompatible.

Matt

On Tue, Oct 10, 2017 at 4:10 PM, Brian Ghigiarelli 
wrote:

> Thanks for the quick response, Matt! Unfortunately, it wasn't letting me
> update the Policies either, but your response did remind to use Firefox vs.
> Chrome. Turns out that when I was clicking on the hamburger menu >
> Policies, Chrome was throwing a JS error on nf-canvas-all.js?1.4.0:47:
> 21377
> with "undefined is not a function"   Looks like it maps to some
> K.resource.startsWith("/policies") line.  Works fine in Firefox, and I can
> add all the policies I want through there.
>
> Thanks again,
> Brian
>
> On Tue, Oct 10, 2017 at 3:58 PM Matt Gilman 
> wrote:
>
> > Brian,
> >
> > NiFi will only grant permissions to the components in the canvas if there
> > is an existing flow.xml.gz in your conf directory. This is due to
> lifecycle
> > constraints when clustered. This is described in the link you provided if
> > you scroll down a little bit and look for the (i) info icon.
> >
> > Thanks
> >
> > Matt
> >
> > On Tue, Oct 10, 2017 at 3:47 PM, Brian Ghigiarelli 
> > wrote:
> >
> > > With a clean install of Apache NiFi 1.4.0 using certificate-based
> > > authentication through file providers, I am able to login to the NiFi
> > > canvas, but it is not authorizing me (the Initial Admin Identity) to
> > > perform any tasks. I'm following the first example configuration at
> > > https://nifi.apache.org/docs/nifi-docs/html/administration-
> > > guide.html#initial-admin-identity.
> > > I
> > > can see that the authorizations.xml file is being generated with the
> same
> > > UUID as the user that is generated in users.xml, and that user has
> > entries
> > > in the following policies:
> > >
> > >- /flow  (R)
> > >- /restricted-components (W)
> > >- /tenants (R)
> > >- /tenants (W)
> > >- /policies (R)
> > >- /policies (W)
> > >- /controller (R)
> > >- /controller (W)
> > >
> > > Based on the docs, a few pieces of the authorizers.xml file changed
> from
> > > 1.3.0 to 1.4.0, and I changed the nifi.properties
> > > nifi.security.user.authorizer to managed-authorizer. Any ideas what I'm
> > > missing here? Or where to begin debugging?
> > >
> > > Thanks,
> > > Brian
> > >
> >
>