[jira] [Updated] (NIFI-13337) Column sizes when listing flowfiles in queue
[ https://issues.apache.org/jira/browse/NIFI-13337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13337: --- Status: Patch Available (was: In Progress) > Column sizes when listing flowfiles in queue > > > Key: NIFI-13337 > URL: https://issues.apache.org/jira/browse/NIFI-13337 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Pierre Villard > Assignee: Matt Gilman >Priority: Major > Attachments: Screenshot 2024-06-02 at 13.59.28.png > > Time Spent: 10m > Remaining Estimate: 0h > > !Screenshot 2024-06-02 at 13.59.28.png|width=964,height=224! > It seems like columns cannot be resized. If that's correct, I believe the > defaults could be a bit better. In particular the columns 'Position' and > 'UUID' seem overly large (although we know the maximum size), while the > column 'Filename' could be larger. > As a side note, there is now one more click to get to flow file content, > details, provenance, etc, as we now have to click to get a menu instead of > having icons. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13354) Prepare frontend codebase for co-location with out UIs
Matt Gilman created NIFI-13354: -- Summary: Prepare frontend codebase for co-location with out UIs Key: NIFI-13354 URL: https://issues.apache.org/jira/browse/NIFI-13354 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman NiFi is comprised of numerous UIs. These UIs exist within different maven modules because of they live in different parts of the codebase and they are packaged in different NARs. This is makes it difficult to reuse shared components, styles, dependencies, etc. This Jira is tracking the migration of the recently rewritten NiFi UI to a top level maven module. This will establish a place where subsequent UIs (custom UIs, documentation, data viewers, etc) can be added. Once all the UIs have been updated, we will be left with a single maven module that produces a single artifact of all built UIs. The existing WARs which currently package the UIs will be responsible for unpacking the front end artifact and copying the applications into the WAR staging directory. In the end, we'll have a single place for all UIs to be colocated where they can easily share reusable components and styles. Further it will be a single place for front end dependencies to be managed. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13337) Column sizes when listing flowfiles in queue
[ https://issues.apache.org/jira/browse/NIFI-13337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13337: -- Assignee: Matt Gilman > Column sizes when listing flowfiles in queue > > > Key: NIFI-13337 > URL: https://issues.apache.org/jira/browse/NIFI-13337 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Pierre Villard > Assignee: Matt Gilman >Priority: Major > Attachments: Screenshot 2024-06-02 at 13.59.28.png > > > !Screenshot 2024-06-02 at 13.59.28.png|width=964,height=224! > It seems like columns cannot be resized. If that's correct, I believe the > defaults could be a bit better. In particular the columns 'Position' and > 'UUID' seem overly large (although we know the maximum size), while the > column 'Filename' could be larger. > As a side note, there is now one more click to get to flow file content, > details, provenance, etc, as we now have to click to get a menu instead of > having icons. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12661) Flow Analysis report menu
[ https://issues.apache.org/jira/browse/NIFI-12661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-12661. Resolution: Duplicate > Flow Analysis report menu > - > > Key: NIFI-12661 > URL: https://issues.apache.org/jira/browse/NIFI-12661 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Shane Ardell >Assignee: Shane Ardell >Priority: Major > > Implement the work from [https://github.com/apache/nifi/pull/8273] in the new > UI. Link to original ticket here: > https://issues.apache.org/jira/browse/NIFI-11520 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13350) Unable to Edit Parameter
[
https://issues.apache.org/jira/browse/NIFI-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-13350:
---
Status: Patch Available (was: In Progress)
> Unable to Edit Parameter
>
>
> Key: NIFI-13350
> URL: https://issues.apache.org/jira/browse/NIFI-13350
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Matt Gilman
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Unable to Edit Parameter in New Parameter Context dialog.
> {noformat}
> TypeError: this.editParameter is not a function
> at _ParameterTable.editClicked (parameter-table.component.ts:277:14)
> at ParameterTable_td_14_Conditional_6_Template_button_click_0_listener
> (parameter-table.component.html:125:72)
> at executeListenerWithErrorHandling (core.mjs:25629:16)
> at wrapListenerIn_markDirtyAndPreventDefault (core.mjs:25669:22)
> at HTMLButtonElement. (platform-browser.mjs:749:112)
> at _ZoneDelegate.invokeTask (zone.js:403:31)
> at core.mjs:18229:55
> at AsyncStackTaggingZoneSpec.onInvokeTask (core.mjs:18229:36)
> at _ZoneDelegate.invokeTask (zone.js:402:36)
> at Object.onInvokeTask (core.mjs:18542:33){noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-13350) Unable to Edit Parameter
Matt Gilman created NIFI-13350:
--
Summary: Unable to Edit Parameter
Key: NIFI-13350
URL: https://issues.apache.org/jira/browse/NIFI-13350
Project: Apache NiFi
Issue Type: Sub-task
Components: Core Framework
Reporter: Matt Gilman
Assignee: Matt Gilman
Unable to Edit Parameter in New Parameter Context dialog.
{noformat}
TypeError: this.editParameter is not a function
at _ParameterTable.editClicked (parameter-table.component.ts:277:14)
at ParameterTable_td_14_Conditional_6_Template_button_click_0_listener
(parameter-table.component.html:125:72)
at executeListenerWithErrorHandling (core.mjs:25629:16)
at wrapListenerIn_markDirtyAndPreventDefault (core.mjs:25669:22)
at HTMLButtonElement. (platform-browser.mjs:749:112)
at _ZoneDelegate.invokeTask (zone.js:403:31)
at core.mjs:18229:55
at AsyncStackTaggingZoneSpec.onInvokeTask (core.mjs:18229:36)
at _ZoneDelegate.invokeTask (zone.js:402:36)
at Object.onInvokeTask (core.mjs:18542:33){noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13313) Replace old UI
[ https://issues.apache.org/jira/browse/NIFI-13313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13313: --- Status: Patch Available (was: In Progress) > Replace old UI > -- > > Key: NIFI-13313 > URL: https://issues.apache.org/jira/browse/NIFI-13313 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > With the new UI functionally ready and other UIs (documentations, data > viewers, etc) no longer depending on the old UI it can now be removed. This > Jira is tracking removal of that maven module and any downstream changes. > These include updating of LICENSE/NOTICEs that no longer bundle removed > dependencies and updating the Jetty Server to only deploy the new UI. The new > UI should use "/nifi" context. Existing functionality around authentication > where the back end redirects the user to the UI should be verified. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13329) Fallback to raw viewer when formatted viewer fails
[ https://issues.apache.org/jira/browse/NIFI-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13329: --- Status: Patch Available (was: In Progress) > Fallback to raw viewer when formatted viewer fails > -- > > Key: NIFI-13329 > URL: https://issues.apache.org/jira/browse/NIFI-13329 > Project: Apache NiFi > Issue Type: Bug >Reporter: Pierre Villard > Assignee: Matt Gilman >Priority: Major > Attachments: Screenshot 2024-05-30 at 11.19.23.png > > Time Spent: 10m > Remaining Estimate: 0h > > The formatted viewer (based on the mime.type attribute) recently became the > default. In case the MIME type is wrong, this would return an error when > opening the flowfile's content. It could be nice to catch the error and > fallback to the raw viewer. > !Screenshot 2024-05-30 at 11.19.23.png|width=611,height=150! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13329) Fallback to raw viewer when formatted viewer fails
[ https://issues.apache.org/jira/browse/NIFI-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13329: -- Assignee: Matt Gilman > Fallback to raw viewer when formatted viewer fails > -- > > Key: NIFI-13329 > URL: https://issues.apache.org/jira/browse/NIFI-13329 > Project: Apache NiFi > Issue Type: Bug >Reporter: Pierre Villard > Assignee: Matt Gilman >Priority: Major > Attachments: Screenshot 2024-05-30 at 11.19.23.png > > > The formatted viewer (based on the mime.type attribute) recently became the > default. In case the MIME type is wrong, this would return an error when > opening the flowfile's content. It could be nice to catch the error and > fallback to the raw viewer. > !Screenshot 2024-05-30 at 11.19.23.png|width=611,height=150! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13329) Fallback to raw viewer when formatted viewer fails
[ https://issues.apache.org/jira/browse/NIFI-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851163#comment-17851163 ] Matt Gilman edited comment on NIFI-13329 at 5/31/24 4:55 PM: - So the error is happening while the data viewer is consuming the stream. Once this fails, subsequent attempts to re-read the stream fail. The stream is either accessing the flowfile from the content repo or consuming an http response in clustered mode. To be able to reread the http response, we'd need to hold the arbitrarily large content and is a bigger effort. Would it make sense for this case to render an error message stating that the content does not match the mime type? Or there was an error in processing the content in formatted mode? The UI would render correctly and show Formatted mode with the message. The user could then change the mode to Original or Hex to see those views. It addresses the error page your seeing above. And I think this case is more uncommon. Defaulting to Formatted and having to manually change to Original when the content in the flowfile is wrong is less annoying for the user than defaulting to Original and having to manually change to Formatted when the content in the flowfile is correct. We could consider alternative behaviors in the future as replacement of these data viewers is on the roadmap to continue modernizing the UIs. was (Author: mcgilman): So the error is happening while the data viewer is consuming the stream. Once this fails, subsequent attempts to re-read the stream fail. The stream is either accessing the flowfile from the content repo or consuming an http response in clustered mode. To be able to reread the http response, we'd need to hold the arbitrarily large content and is a bigger effort. Would be make sense for this case to render an error message stating that the content does not match the mime type? Or there was an error in processing the content in formatted mode? The UI would render correctly and show Formatted mode with the message. The user could then change the mode to Original or Hex to see those views. It addresses the error page your seeing above. And I think this case is more uncommon. Defaulting to Formatted and having to manually change to Original when the content in the flowfile is wrong is less annoying for the user than defaulting to Original and having to manually change to Formatted when the content in the flowfile is correct. We could consider alternative behaviors in the future as replacement of these data viewers is on the roadmap to continue modernizing the UIs. > Fallback to raw viewer when formatted viewer fails > -- > > Key: NIFI-13329 > URL: https://issues.apache.org/jira/browse/NIFI-13329 > Project: Apache NiFi > Issue Type: Bug >Reporter: Pierre Villard >Priority: Major > Attachments: Screenshot 2024-05-30 at 11.19.23.png > > > The formatted viewer (based on the mime.type attribute) recently became the > default. In case the MIME type is wrong, this would return an error when > opening the flowfile's content. It could be nice to catch the error and > fallback to the raw viewer. > !Screenshot 2024-05-30 at 11.19.23.png|width=611,height=150! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13329) Fallback to raw viewer when formatted viewer fails
[ https://issues.apache.org/jira/browse/NIFI-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851163#comment-17851163 ] Matt Gilman commented on NIFI-13329: So the error is happening while the data viewer is consuming the stream. Once this fails, subsequent attempts to re-read the stream fail. The stream is either accessing the flowfile from the content repo or consuming an http response in clustered mode. To be able to reread the http response, we'd need to hold the arbitrarily large content and is a bigger effort. Would be make sense for this case to render an error message stating that the content does not match the mime type? Or there was an error in processing the content in formatted mode? The UI would render correctly and show Formatted mode with the message. The user could then change the mode to Original or Hex to see those views. It addresses the error page your seeing above. And I think this case is more uncommon. Defaulting to Formatted and having to manually change to Original when the content in the flowfile is wrong is less annoying for the user than defaulting to Original and having to manually change to Formatted when the content in the flowfile is correct. We could consider alternative behaviors in the future as replacement of these data viewers is on the roadmap to continue modernizing the UIs. > Fallback to raw viewer when formatted viewer fails > -- > > Key: NIFI-13329 > URL: https://issues.apache.org/jira/browse/NIFI-13329 > Project: Apache NiFi > Issue Type: Bug >Reporter: Pierre Villard >Priority: Major > Attachments: Screenshot 2024-05-30 at 11.19.23.png > > > The formatted viewer (based on the mime.type attribute) recently became the > default. In case the MIME type is wrong, this would return an error when > opening the flowfile's content. It could be nice to catch the error and > fallback to the raw viewer. > !Screenshot 2024-05-30 at 11.19.23.png|width=611,height=150! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13329) Fallback to raw viewer when formatted viewer fails
[ https://issues.apache.org/jira/browse/NIFI-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851146#comment-17851146 ] Matt Gilman commented on NIFI-13329: Thanks for clarifying. I wasn't reproducing correctly. I thought the mime type in the attribute was wrong. In this case the attribute was correct but the content was not of that type. So in NiFi the attribute value drives which data viewer is used. In this case, it matched. The error that is happening is a function of this data viewer. The data viewer that handles JSON does not have explicit error handling for this case which is resulting in the error in your screenshot. This behavior also happened before Formatted was made the default. Previously, it required the user to select Formatted first. The downside currently, is that the user never gets the UI where they can attempt to change the mode. The client/browser drives which mode we're in. We may be able to update this data viewer to catch the errors and instead return the content in its original form. But the UI would likely still reflect Formatted mode. The data viewers are actually multiple JSPs included together (header, content, footer). I don't think an error or change in the mode happening in the content can impact the header but I'll need to investigate. It's possible that even if we can't update the selected mode, it would be an improvement over what's happening here. > Fallback to raw viewer when formatted viewer fails > -- > > Key: NIFI-13329 > URL: https://issues.apache.org/jira/browse/NIFI-13329 > Project: Apache NiFi > Issue Type: Bug >Reporter: Pierre Villard >Priority: Major > Attachments: Screenshot 2024-05-30 at 11.19.23.png > > > The formatted viewer (based on the mime.type attribute) recently became the > default. In case the MIME type is wrong, this would return an error when > opening the flowfile's content. It could be nice to catch the error and > fallback to the raw viewer. > !Screenshot 2024-05-30 at 11.19.23.png|width=611,height=150! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13329) Fallback to raw viewer when formatted viewer fails
[ https://issues.apache.org/jira/browse/NIFI-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13329: --- Parent: (was: NIFI-12400) Issue Type: Bug (was: Sub-task) > Fallback to raw viewer when formatted viewer fails > -- > > Key: NIFI-13329 > URL: https://issues.apache.org/jira/browse/NIFI-13329 > Project: Apache NiFi > Issue Type: Bug >Reporter: Pierre Villard >Priority: Major > Attachments: Screenshot 2024-05-30 at 11.19.23.png > > > The formatted viewer (based on the mime.type attribute) recently became the > default. In case the MIME type is wrong, this would return an error when > opening the flowfile's content. It could be nice to catch the error and > fallback to the raw viewer. > !Screenshot 2024-05-30 at 11.19.23.png|width=611,height=150! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-13329) Fallback to raw viewer when formatted viewer fails
[ https://issues.apache.org/jira/browse/NIFI-13329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851091#comment-17851091 ] Matt Gilman commented on NIFI-13329: [~pvillard] Can you provide some more details? I just tried to reproduce this and I am seeing different behavior. Also are you seeing any errors in any of the logs? Thanks. > Fallback to raw viewer when formatted viewer fails > -- > > Key: NIFI-13329 > URL: https://issues.apache.org/jira/browse/NIFI-13329 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Pierre Villard >Priority: Major > Attachments: Screenshot 2024-05-30 at 11.19.23.png > > > The formatted viewer (based on the mime.type attribute) recently became the > default. In case the MIME type is wrong, this would return an error when > opening the flowfile's content. It could be nice to catch the error and > fallback to the raw viewer. > !Screenshot 2024-05-30 at 11.19.23.png|width=611,height=150! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-13331) Make tables more compact
[
https://issues.apache.org/jira/browse/NIFI-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851072#comment-17851072
]
Matt Gilman edited comment on NIFI-13331 at 5/31/24 1:13 PM:
-
In the new UI we are using the Angular Material. Their APIs allow the density
of the table to be configured. We are currently using the densest option.
{noformat}
@include mat.table-density(-4);{noformat}
Material design is definitely less compact than the old NiFi UI. We could
consider not using their API and instead overriding some of their styles.
However, that may introduce upgrade challenges down the road as their is no
guarantee those styles or the generated mark up remains the same from release
to release. Because we opted to use Material design we probably shouldn't try
to introduce changes that diverge from it.
Another option we could consider is building a custom table component or
bringing in a separate dependency for it but each of those options have own
consequences.
was (Author: mcgilman):
In the new UI we are using the Angular Material. Their APIs allow the density
of the table to be configured. We are currently using the densest option.
{noformat}
@include mat.table-density(-4);{noformat}
Material design is definitely less compact than the old NiFi UI. We could
consider not using their API and instead overriding some of their styles.
However, that may introduce upgrade challenges down the road as their is no
guarantee those styles or the generated mark up remains the same from release
to release. We could also consider building a custom table component or
bringing in a separate dependency for it but that what would be a big effort.
> Make tables more compact
>
>
> Key: NIFI-13331
> URL: https://issues.apache.org/jira/browse/NIFI-13331
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core UI
> Reporter: Matt Gilman
>Priority: Major
>
> The rows in the tables in the old UI were more compact than the new UI. We
> should consider options for making the tables in the new UI more dense.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-13331) Make tables more compact
[
https://issues.apache.org/jira/browse/NIFI-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17851072#comment-17851072
]
Matt Gilman commented on NIFI-13331:
In the new UI we are using the Angular Material. Their APIs allow the density
of the table to be configured. We are currently using the densest option.
{noformat}
@include mat.table-density(-4);{noformat}
Material design is definitely less compact than the old NiFi UI. We could
consider not using their API and instead overriding some of their styles.
However, that may introduce upgrade challenges down the road as their is no
guarantee those styles or the generated mark up remains the same from release
to release. We could also consider building a custom table component or
bringing in a separate dependency for it but that what would be a big effort.
> Make tables more compact
>
>
> Key: NIFI-13331
> URL: https://issues.apache.org/jira/browse/NIFI-13331
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core UI
> Reporter: Matt Gilman
>Priority: Major
>
> The rows in the tables in the old UI were more compact than the new UI. We
> should consider options for making the tables in the new UI more dense.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [DISCUSS] Progress Update on new UI
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 > > > > > > > > > > > > > > >
[jira] [Created] (NIFI-13331) Make table more compact
Matt Gilman created NIFI-13331: -- Summary: Make table more compact Key: NIFI-13331 URL: https://issues.apache.org/jira/browse/NIFI-13331 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman The rows in the tables in the old UI were more compact than the new UI. We should consider options for making the tables in the new UI more dense. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13331) Make tables more compact
[ https://issues.apache.org/jira/browse/NIFI-13331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13331: --- Summary: Make tables more compact (was: Make table more compact) > Make tables more compact > > > Key: NIFI-13331 > URL: https://issues.apache.org/jira/browse/NIFI-13331 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman >Priority: Major > > The rows in the tables in the old UI were more compact than the new UI. We > should consider options for making the tables in the new UI more dense. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13246) Move actions into kebab menu
[ https://issues.apache.org/jira/browse/NIFI-13246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13246: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Move actions into kebab menu > > > Key: NIFI-13246 > URL: https://issues.apache.org/jira/browse/NIFI-13246 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Fix For: 2.0.0-M4 > > Time Spent: 0.5h > Remaining Estimate: 0h > > View Provenance event > View FlowFile > View Documentation > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-13234) Unauthorized canvas components issues
[ https://issues.apache.org/jira/browse/NIFI-13234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-13234. Fix Version/s: 2.0.0-M4 Resolution: Fixed > Unauthorized canvas components issues > - > > Key: NIFI-13234 > URL: https://issues.apache.org/jira/browse/NIFI-13234 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Fix For: 2.0.0-M4 > > Attachments: Screenshot 2024-05-14 at 1.01.15 PM.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > There are color and contrast ratio issues for unauthorized components on the > canvas: > > !Screenshot 2024-05-14 at 1.01.15 PM.png|width=415,height=222! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported features
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) *** Support Processor Details dialog (NIFI-13316) *** Support Connection Details dialog (NIFI-13317) * Counters (NIFI-12415) ** Counter table has extra unnecessary can modify check (NIFI-12948) * Bulletin Board (NIFI-12560) * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) ** Clustering (NIFI-12807) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Node table (Disconnect/Connect/Load Balance/Etc) (NIFI-13053) ** Status History - node specific values (NIFI-12848) * Flow Configuration History (NIFI-12754) ** ActionEntity.action should be optional (NIFI-12948) * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) ** Don't show users or groups in create/edit dialog is there are none (NIFI-12948) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) ** Select Empty by default (NIFI-12948) * Help (NIFI-12795) * About (NIFI-13094) * Show Upstream/Downstream * Align (NIFI-13162) * Replay last event (NIFI-12445) * List Queue (NIFI-12589) ** Clustering (NIFI-12807) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) ** Clustering (NIFI-13005) * Change Component Version (NIFI-13034) * Consider PG permissions in Toolbox (NIFI-12683) * PG Version (NIFI-12963 & NIFI-12995) ** Start (NIFI-12963) ** Commit (NIFI-12963) ** Force Commit (NIFI-12963) ** Show changes (NIFI-12995) ** Revert changes (NIFI-12995) ** Change Flow version (NIFI-12995) ** Stop (NIFI-12963) * Configure PG (NIFI-12417) * Configure Label (NIFI-13081) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs ** Disable and Configure * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Status Bar ** Stop and Configure ** Open Custom UI (NIFI-12958) ** Property History (NIFI-13047) ** Unable to re-add any removed Property (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification (NIFI-13247) * Terminate Threads (context menu) (NIFI-13068) * Enable/Disable (context menu/operate panel) (NIFI-13078) * More Details (Processor, Controller Service, Reporting Task) (NIFI-13062) * Download Flow (NIFI-13029) * Create RPG (NIFI-12758) * Configure RPG (NIFI-12774) * RPG Remote Ports (NIFI-12778) * RPG Go To (NIFI-12759) * RPG Refresh (NIFI-12761) * Color (context menu/operate panel) (NIFI-13226) * Move to Front (NIFI-13044) * Copy/Paste (context menu/operate panel) (NIFI-13059) * Add/Update Info Icons in dialogs throughout the application (NIFI-13092) * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build (NIFI-12941) * Update all API calls to consider disconnect node confirmation (NIFI-13001) * Update API calls to use uiOnly flag (NIFI-12950) * Use polling interval from API * Load FlowConfiguration in guard (NIFI-12948) * Routing error handling (NIFI-13104) * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer (NIFI-1
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported features
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) *** Support Processor Details dialog (NIFI-13316) *** Support Connection Details dialog (NIFI-13317) * Counters (NIFI-12415) ** Counter table has extra unnecessary can modify check (NIFI-12948) * Bulletin Board (NIFI-12560) * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) ** Clustering (NIFI-12807) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Node table (Disconnect/Connect/Load Balance/Etc) (NIFI-13053) ** Status History - node specific values (NIFI-12848) * Flow Configuration History (NIFI-12754) ** ActionEntity.action should be optional (NIFI-12948) * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) ** Don't show users or groups in create/edit dialog is there are none (NIFI-12948) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) ** Select Empty by default (NIFI-12948) * Help (NIFI-12795) * About (NIFI-13094) * Show Upstream/Downstream * Align (NIFI-13162) * Replay last event (NIFI-12445) * List Queue (NIFI-12589) ** Clustering (NIFI-12807) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) ** Clustering (NIFI-13005) * Change Component Version (NIFI-13034) * Consider PG permissions in Toolbox (NIFI-12683) * PG Version (NIFI-12963 & NIFI-12995) ** Start (NIFI-12963) ** Commit (NIFI-12963) ** Force Commit (NIFI-12963) ** Show changes (NIFI-12995) ** Revert changes (NIFI-12995) ** Change Flow version (NIFI-12995) ** Stop (NIFI-12963) * Configure PG (NIFI-12417) * Configure Label (NIFI-13081) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs ** Disable and Configure (NIFI-13319) * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Status Bar ** Stop and Configure (NIFI-13318) ** Open Custom UI (NIFI-12958) ** Property History (NIFI-13047) ** Unable to re-add any removed Property (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification (NIFI-13247) * Terminate Threads (context menu) (NIFI-13068) * Enable/Disable (context menu/operate panel) (NIFI-13078) * More Details (Processor, Controller Service, Reporting Task) (NIFI-13062) * Download Flow (NIFI-13029) * Create RPG (NIFI-12758) * Configure RPG (NIFI-12774) * RPG Remote Ports (NIFI-12778) * RPG Go To (NIFI-12759) * RPG Refresh (NIFI-12761) * Color (context menu/operate panel) (NIFI-13226) * Move to Front (NIFI-13044) * Copy/Paste (context menu/operate panel) (NIFI-13059) * Add/Update Info Icons in dialogs throughout the application (NIFI-13092) * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build (NIFI-12941) * Update all API calls to consider disconnect node confirmation (NIFI-13001) * Update API calls to use uiOnly flag (NIFI-12950) * Use polling interval from API * Load FlowConfiguration in guard (NIFI-12948) * Routing error handling (NIFI-13104) * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-1
Re: [DISCUSS] Progress Update on new UI
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 > > > > > >
[jira] [Updated] (NIFI-13314) Update guides for new UI
[ https://issues.apache.org/jira/browse/NIFI-13314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13314: --- Description: The new NiFi UI leverages the same general UX as the old UI. However, there are some differences that have evolved as the new UI was built. This Jira is tracking needed changes to the documentation and guides. While there are many details in these guides, we should prioritize updating areas where the UX has changed substantially from the old UI. * Managing Remote Ports * Process Group Configuration * Process Group Controller Services * Color Processor/Label * Flow Configuration History Sub-tasks can be added to this Jira for landing each of these updates. was: The new NiFi UI leverages the same general UX as the old UI. However, there are some differences that have evolved as the new UI was built. This Jira is tracking needed changes to the documentation and guides. While is a ton of details in these guides, we should prioritize updating areas where the UX has changed substantially from the old UI. * Managing Remote Ports * Process Group Configuration * Process Group Controller Services * Color Processor/Label * Flow Configuration History Sub-tasks can be added to this Jira for landing each of these updates. > Update guides for new UI > > > Key: NIFI-13314 > URL: https://issues.apache.org/jira/browse/NIFI-13314 > Project: Apache NiFi > Issue Type: Task > Components: Documentation Website > Reporter: Matt Gilman >Priority: Major > > The new NiFi UI leverages the same general UX as the old UI. However, there > are some differences that have evolved as the new UI was built. This Jira is > tracking needed changes to the documentation and guides. While there are many > details in these guides, we should prioritize updating areas where the UX has > changed substantially from the old UI. > * Managing Remote Ports > * Process Group Configuration > * Process Group Controller Services > * Color Processor/Label > * Flow Configuration History > Sub-tasks can be added to this Jira for landing each of these updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[DISCUSS] Progress Update on new UI
Team, About a month ago a [DISCUSS] thread was sent regarding the UI updates and requesting that any future contributions target both old and new UIs. Since then there has been substantial progress as we continue to close the gap on feature parity with the old UI. Only a few features remain [1] [2] [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
[jira] [Updated] (NIFI-13321) Fix mocking of child components in unit tests
[ https://issues.apache.org/jira/browse/NIFI-13321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13321: --- Status: Patch Available (was: In Progress) > Fix mocking of child components in unit tests > - > > Key: NIFI-13321 > URL: https://issues.apache.org/jira/browse/NIFI-13321 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The existing mocking of child components in unit tests was incorrect and > would often require the test bed to provide dependencies of the child > component. This should be fixed so that unit tests can focus on just the > component in question and not anything functionality of a child component. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13321) Fix mocking of child components in unit tests
Matt Gilman created NIFI-13321: -- Summary: Fix mocking of child components in unit tests Key: NIFI-13321 URL: https://issues.apache.org/jira/browse/NIFI-13321 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman The existing mocking of child components in unit tests was incorrect and would often require the test bed to provide dependencies of the child component. This should be fixed so that unit tests can focus on just the component in question and not anything functionality of a child component. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13319) Add support to Stop and Disable from CS Configuration
Matt Gilman created NIFI-13319: -- Summary: Add support to Stop and Disable from CS Configuration Key: NIFI-13319 URL: https://issues.apache.org/jira/browse/NIFI-13319 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman While a Service is enabled, the configuration dialog is shown in read only form. When the user wants to make configuration changes, they need to disable the component before they can open the Edit dialog. This Jira is tracking the introduction of being able to disable the enabled Service and automatically have the Edit dialog being opened to reduce the interaction and number of clicks needed to disable the component manually. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13318) Add support to Stop and Configure from Processor Configuration
Matt Gilman created NIFI-13318: -- Summary: Add support to Stop and Configure from Processor Configuration Key: NIFI-13318 URL: https://issues.apache.org/jira/browse/NIFI-13318 Project: Apache NiFi Issue Type: Sub-task Reporter: Matt Gilman While a Processor is running, the configuration dialog is shown in read only form. When the user wants to make configuration changes, they need to stop the component and wait for active threads to stop before they can open the Edit dialog. This Jira is tracking the introduction of being able to stop the running Processor and automatically have the Edit dialog being opened to reduce the interaction and number of clicks needed to stop the component manually. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13317) Read only Connection Configuration from Summary
Matt Gilman created NIFI-13317: -- Summary: Read only Connection Configuration from Summary Key: NIFI-13317 URL: https://issues.apache.org/jira/browse/NIFI-13317 Project: Apache NiFi Issue Type: Sub-task Reporter: Matt Gilman >From the Summary page NiFi should support showing the Connection configuration >dialog in read only form. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13316) Read only Processor Configuration from Summary
Matt Gilman created NIFI-13316: -- Summary: Read only Processor Configuration from Summary Key: NIFI-13316 URL: https://issues.apache.org/jira/browse/NIFI-13316 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman >From the Summary page NiFi should support showing the Processor configuration >dialog in read only form. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported features
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Summary: Remaining items to migrate UI to currently supported features (was: Remaining items to migrate UI to currently supported/active framework) > Remaining items to migrate UI to currently supported features > - > > Key: NIFI-12400 > URL: https://issues.apache.org/jira/browse/NIFI-12400 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 2h 50m > Remaining Estimate: 0h > > The purpose of this Jira is to track all remaining items following the > initial commit [1] for NIFI-11481. The description will be kept up to date > with remaining features, tasks, and improvements. As each items is worked, a > new sub task Jira will be created and referenced in this description. > * Support Parameters in Properties with Allowable Values (NIFI-12401) > * Summary (NIFI-12437) > ** Remaining work not addressed in initial Jira: > *** input ports (NIFI-12504) > *** output ports (NIFI-12504) > *** remote process groups (NIFI-12504) > *** process groups (NIFI-12504) > *** connections (NIFI-12504) > *** System Diagnostics (NIFI-12505) > *** support for cluster-specific ui elements (NIFI-12537) > *** Add pagination (NIFI-12552) > *** Support Processor Details dialog > *** Support Connection Details dialog > * Counters (NIFI-12415) > ** Counter table has extra unnecessary can modify check (NIFI-12948) > * Bulletin Board (NIFI-12560) > * Provenance (NIFI-12445) > ** Event Listing (NIFI-12445) > ** Search (NIFI-12445) > ** Event Dialog (NIFI-12445) > ** Lineage (NIFI-12485) > ** Replay from context menu (NIFI-12445) > ** Clustering (NIFI-12807) > * Configure Reporting Task (NIFI-12563) > * Flow Analysis Rules (NIFI-12588) > * Registry Clients (NIFI-12486) > * Import from Registry (NIFI-12734) > * Parameter Providers (NIFI-12622) > ** Fetch parameters from provider, map to parameter context (dialog) - > (NIFI-12665) > * Cluster > ** Node table (Disconnect/Connect/Load Balance/Etc) (NIFI-13053) > ** Status History - node specific values (NIFI-12848) > * Flow Configuration History (NIFI-12754) > ** ActionEntity.action should be optional (NIFI-12948) > * Node Status History (NIFI-12553) > * Status history for components from canvas context menu (NIFI-12553) > * Users (NIFI-12543) > ** Don't show users or groups in create/edit dialog is there are none > (NIFI-12948) > * Policies (NIFI-12548) > ** Overridden policy Empty or Copy (NIFI-12679) > ** Select Empty by default (NIFI-12948) > * Help (NIFI-12795) > * About (NIFI-13094) > * Show Upstream/Downstream > * Align (NIFI-13162) > * Replay last event (NIFI-12445) > * List Queue (NIFI-12589) > ** Clustering (NIFI-12807) > * Empty [all] Queue (NIFI-12604) > * View Content (NIFI-12589 and NIFI-12445) > * View State (NIFI-12611) > ** Clustering (NIFI-13005) > * Change Component Version (NIFI-13034) > * Consider PG permissions in Toolbox (NIFI-12683) > * PG Version (NIFI-12963 & NIFI-12995) > ** Start (NIFI-12963) > ** Commit (NIFI-12963) > ** Force Commit (NIFI-12963) > ** Show changes (NIFI-12995) > ** Revert changes (NIFI-12995) > ** Change Flow version (NIFI-12995) > ** Stop (NIFI-12963) > * Configure PG (NIFI-12417) > * Configure Label (NIFI-13081) > * Process Group Services (NIFI-12425) > ** Listing (NIFI-12425) > ** Create (NIFI-12425) > ** Configure (NIFI-12425) > ** Delete (NIFI-12425) > ** Enable (NIFI-12529) > ** Disable (NIFI-12529) > ** Improve layout and breadcrumbs > ** Disable and Configure > * Configure Processor > ** Service Link (NIFI-12425) > ** Create inline Service (NIFI-12425) > ** Parameter Link (NIFI-12502) > ** Convert to Parameter (NIFI-12502) > ** Fix issue with Property Editor width (NIFI-12547) > ** Status Bar > ** Stop and Configure > ** Open Custom UI (NIFI-12958) > ** Property History (NIFI-13047) > ** Unable to re-add any removed Property (NIFI-12743) > ** Shift-Enter new line when editing Property (NIFI-12743) > * Property Verification (NIFI-13247) > * Terminate Threads (context menu) (NIFI-13068) > * Enable/Disable (context menu/operate panel) (NIFI-13078) > * More Details (Processor, Controller Service, Reporting Task) (NIFI-13062) > * Download Flow (NIFI-13029) > * Cre
[jira] [Resolved] (NIFI-12873) Time inputs don't match dark mode styling
[ https://issues.apache.org/jira/browse/NIFI-12873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-12873. Resolution: Won't Fix > Time inputs don't match dark mode styling > - > > Key: NIFI-12873 > URL: https://issues.apache.org/jira/browse/NIFI-12873 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: James Elliott >Priority: Major > Attachments: Screenshot 2024-03-07 at 11.20.29 AM.png, Screenshot > 2024-03-19 at 10.40.32 AM.png, Screenshot 2024-03-19 at 10.40.42 AM.png > > > Inputs with type="time" get an icon that launches a time selection popup. > Unfortunately the icon is always dark, even in dark mode. The popup doesn't > have styling applied either. > !Screenshot 2024-03-07 at 11.20.29 AM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13269) Parameter reference list is randomly ordered or not ordered
[ https://issues.apache.org/jira/browse/NIFI-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13269: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Parameter reference list is randomly ordered or not ordered > --- > > Key: NIFI-13269 > URL: https://issues.apache.org/jira/browse/NIFI-13269 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Julien G. >Assignee: Rob Fellows >Priority: Major > Fix For: 2.0.0-M4 > > Attachments: Screenshot 2024-05-22 at 3.49.48 PM.png, > image-2024-05-21-11-04-26-571.png, image-2024-05-22-22-12-46-877.png, > legacy.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > When referencing a parameter in a Controller Service, a list of the availabe > parameter is displayed. > In the new UI, the list is randomly ordered or not ordered at all. > !image-2024-05-21-11-04-26-571.png|thumbnail! > It makes it hard to find a parameter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) *** Support Processor Details dialog *** Support Connection Details dialog * Counters (NIFI-12415) ** Counter table has extra unnecessary can modify check (NIFI-12948) * Bulletin Board (NIFI-12560) * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) ** Clustering (NIFI-12807) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Node table (Disconnect/Connect/Load Balance/Etc) (NIFI-13053) ** Status History - node specific values (NIFI-12848) * Flow Configuration History (NIFI-12754) ** ActionEntity.action should be optional (NIFI-12948) * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) ** Don't show users or groups in create/edit dialog is there are none (NIFI-12948) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) ** Select Empty by default (NIFI-12948) * Help (NIFI-12795) * About (NIFI-13094) * Show Upstream/Downstream * Align (NIFI-13162) * Replay last event (NIFI-12445) * List Queue (NIFI-12589) ** Clustering (NIFI-12807) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) ** Clustering (NIFI-13005) * Change Component Version (NIFI-13034) * Consider PG permissions in Toolbox (NIFI-12683) * PG Version (NIFI-12963 & NIFI-12995) ** Start (NIFI-12963) ** Commit (NIFI-12963) ** Force Commit (NIFI-12963) ** Show changes (NIFI-12995) ** Revert changes (NIFI-12995) ** Change Flow version (NIFI-12995) ** Stop (NIFI-12963) * Configure PG (NIFI-12417) * Configure Label (NIFI-13081) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs ** Disable and Configure * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Status Bar ** Stop and Configure ** Open Custom UI (NIFI-12958) ** Property History (NIFI-13047) ** Unable to re-add any removed Property (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification (NIFI-13247) * Terminate Threads (context menu) (NIFI-13068) * Enable/Disable (context menu/operate panel) (NIFI-13078) * More Details (Processor, Controller Service, Reporting Task) (NIFI-13062) * Download Flow (NIFI-13029) * Create RPG (NIFI-12758) * Configure RPG (NIFI-12774) * RPG Remote Ports (NIFI-12778) * RPG Go To (NIFI-12759) * RPG Refresh (NIFI-12761) * Color (context menu/operate panel) (NIFI-13226) * Move to Front (NIFI-13044) * Copy/Paste (context menu/operate panel) (NIFI-13059) * Add/Update Info Icons in dialogs throughout the application (NIFI-13092) * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build (NIFI-12941) * Update all API calls to consider disconnect node confirmation (NIFI-13001) * Update API calls to use uiOnly flag (NIFI-12950) * Use polling interval from API * Load FlowConfiguration in guard (NIFI-12948) * Routing error handling (NIFI-13104) * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer (NIFI-13100) ** Parameter Cont
[jira] [Created] (NIFI-13314) Update guides for new UI
Matt Gilman created NIFI-13314: -- Summary: Update guides for new UI Key: NIFI-13314 URL: https://issues.apache.org/jira/browse/NIFI-13314 Project: Apache NiFi Issue Type: Task Components: Documentation Website Reporter: Matt Gilman The new NiFi UI leverages the same general UX as the old UI. However, there are some differences that have evolved as the new UI was built. This Jira is tracking needed changes to the documentation and guides. While is a ton of details in these guides, we should prioritize updating areas where the UX has changed substantially from the old UI. * Managing Remote Ports * Process Group Configuration * Process Group Controller Services * Color Processor/Label * Flow Configuration History Sub-tasks can be added to this Jira for landing each of these updates. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) *** Support Processor Details dialog *** Support Connection Details dialog * Counters (NIFI-12415) ** Counter table has extra unnecessary can modify check (NIFI-12948) * Bulletin Board (NIFI-12560) * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) ** Clustering (NIFI-12807) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Node table (Disconnect/Connect/Load Balance/Etc) (NIFI-13053) ** Status History - node specific values (NIFI-12848) * Flow Configuration History (NIFI-12754) ** ActionEntity.action should be optional (NIFI-12948) * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) ** Don't show users or groups in create/edit dialog is there are none (NIFI-12948) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) ** Select Empty by default (NIFI-12948) * Help (NIFI-12795) * About (NIFI-13094) * Show Upstream/Downstream * Align (NIFI-13162) * Replay last event (NIFI-12445) * List Queue (NIFI-12589) ** Clustering (NIFI-12807) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) ** Clustering (NIFI-13005) * Change Component Version (NIFI-13034) * Consider PG permissions in Toolbox (NIFI-12683) * PG Version (NIFI-12963 & NIFI-12995) ** Start (NIFI-12963) ** Commit (NIFI-12963) ** Force Commit (NIFI-12963) ** Show changes (NIFI-12995) ** Revert changes (NIFI-12995) ** Change Flow version (NIFI-12995) ** Stop (NIFI-12963) * Configure PG (NIFI-12417) * Configure Label (NIFI-13081) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs ** Disable and Configure * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Status Bar ** Stop and Configure ** Open Custom UI (NIFI-12958) ** Property History (NIFI-13047) ** Unable to re-add any removed Property (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification (NIFI-13247) * Terminate Threads (context menu) (NIFI-13068) * Enable/Disable (context menu/operate panel) (NIFI-13078) * More Details (Processor, Controller Service, Reporting Task) (NIFI-13062) * Download Flow (NIFI-13029) * Create RPG (NIFI-12758) * Configure RPG (NIFI-12774) * RPG Remote Ports (NIFI-12778) * RPG Go To (NIFI-12759) * RPG Refresh (NIFI-12761) * Color (context menu/operate panel) (NIFI-13226) * Move to Front (NIFI-13044) * Copy/Paste (context menu/operate panel) (NIFI-13059) * Add/Update Info Icons in dialogs throughout the application (NIFI-13092) * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build (NIFI-12941) * Update all API calls to consider disconnect node confirmation (NIFI-13001) * Update API calls to use uiOnly flag (NIFI-12950) * Use polling interval from API * Load FlowConfiguration in guard (NIFI-12948) * Routing error handling (NIFI-13104) * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer (NIFI-13100) ** Parameter Cont
[jira] [Created] (NIFI-13313) Replace old UI
Matt Gilman created NIFI-13313: -- Summary: Replace old UI Key: NIFI-13313 URL: https://issues.apache.org/jira/browse/NIFI-13313 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman With the new UI functionally ready and other UIs (documentations, data viewers, etc) no longer depending on the old UI it can now be removed. This Jira is tracking removal of that maven module and any downstream changes. These include updating of LICENSE/NOTICEs that no longer bundle removed dependencies and updating the Jetty Server to only deploy the new UI. The new UI should use "/nifi" context. Existing functionality around authentication where the back end redirects the user to the UI should be verified. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13299) Prevent negative numbers in concurrent tasks
[ https://issues.apache.org/jira/browse/NIFI-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13299: --- Status: Patch Available (was: In Progress) > Prevent negative numbers in concurrent tasks > > > Key: NIFI-13299 > URL: https://issues.apache.org/jira/browse/NIFI-13299 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > For inputs like concurrent tasks we know that negative values are not > allowed. We should prevent them before the user can submit the form. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13299) Prevent negative numbers in concurrent tasks
[ https://issues.apache.org/jira/browse/NIFI-13299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13299: -- Assignee: Matt Gilman > Prevent negative numbers in concurrent tasks > > > Key: NIFI-13299 > URL: https://issues.apache.org/jira/browse/NIFI-13299 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > > For inputs like concurrent tasks we know that negative values are not > allowed. We should prevent them before the user can submit the form. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13284) Consider filtering current-canvas-route
[ https://issues.apache.org/jira/browse/NIFI-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13284: --- Status: Patch Available (was: In Progress) > Consider filtering current-canvas-route > --- > > Key: NIFI-13284 > URL: https://issues.apache.org/jira/browse/NIFI-13284 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently, the canvas tracks the current route so the user can be returned to > where they were when returning to the canvas. We should consider filtering > out any `edit` routes so that the user is returned to the place in the canvas > rather then in an Edit dialog. > Since dialogs are only and must be closed prior to using most navigation > controls this won't happen regularly. However a user routes through a Go To > command it will. By filtering out `edit` routes, it may be less confusing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13303) Remove text indicating property verification is disabled
[ https://issues.apache.org/jira/browse/NIFI-13303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13303: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Remove text indicating property verification is disabled > > > Key: NIFI-13303 > URL: https://issues.apache.org/jira/browse/NIFI-13303 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Fix For: 2.0.0-M4 > > Time Spent: 0.5h > Remaining Estimate: 0h > > The text "Property verification is disabled" is extraneous. Don't display it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13284) Consider filtering current-canvas-route
[ https://issues.apache.org/jira/browse/NIFI-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13284: -- Assignee: Matt Gilman > Consider filtering current-canvas-route > --- > > Key: NIFI-13284 > URL: https://issues.apache.org/jira/browse/NIFI-13284 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > > Currently, the canvas tracks the current route so the user can be returned to > where they were when returning to the canvas. We should consider filtering > out any `edit` routes so that the user is returned to the place in the canvas > rather then in an Edit dialog. > Since dialogs are only and must be closed prior to using most navigation > controls this won't happen regularly. However a user routes through a Go To > command it will. By filtering out `edit` routes, it may be less confusing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13299) Prevent negative numbers in concurrent tasks
Matt Gilman created NIFI-13299: -- Summary: Prevent negative numbers in concurrent tasks Key: NIFI-13299 URL: https://issues.apache.org/jira/browse/NIFI-13299 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman For inputs like concurrent tasks we know that negative values are not allowed. We should prevent them before the user can submit the form. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13270) Selected tab is not saved
[ https://issues.apache.org/jira/browse/NIFI-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13270: --- Status: Patch Available (was: In Progress) > Selected tab is not saved > - > > Key: NIFI-13270 > URL: https://issues.apache.org/jira/browse/NIFI-13270 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Julien G. > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > In a component such as a processor, when we select the Properties tab, the > selection was saved in the previous UI, so when we switch to another > processor, we don't need to select the tab again. In the new UI, we have to > select it again each time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13270) Selected tab is not saved
[ https://issues.apache.org/jira/browse/NIFI-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13270: -- Assignee: Matt Gilman > Selected tab is not saved > - > > Key: NIFI-13270 > URL: https://issues.apache.org/jira/browse/NIFI-13270 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Julien G. > Assignee: Matt Gilman >Priority: Major > > In a component such as a processor, when we select the Properties tab, the > selection was saved in the previous UI, so when we switch to another > processor, we don't need to select the tab again. In the new UI, we have to > select it again each time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13285) Fit on Enter PG
[ https://issues.apache.org/jira/browse/NIFI-13285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13285: --- Status: Patch Available (was: In Progress) > Fit on Enter PG > --- > > Key: NIFI-13285 > URL: https://issues.apache.org/jira/browse/NIFI-13285 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When navigating into a PG where there is no saved viewport position we should > consider executing a fit action so that flow is shown centered on the canvas. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13285) Fit on Enter PG
[ https://issues.apache.org/jira/browse/NIFI-13285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13285: -- Assignee: Matt Gilman > Fit on Enter PG > --- > > Key: NIFI-13285 > URL: https://issues.apache.org/jira/browse/NIFI-13285 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > > When navigating into a PG where there is no saved viewport position we should > consider executing a fit action so that flow is shown centered on the canvas. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13286) Empty All Queues issues
[ https://issues.apache.org/jira/browse/NIFI-13286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13286: --- Status: Patch Available (was: In Progress) > Empty All Queues issues > --- > > Key: NIFI-13286 > URL: https://issues.apache.org/jira/browse/NIFI-13286 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Empty All Queues should conditionally reload the current PG or the selected > child PG depending on the subject of the action. Currently, the action > assumes it's being executed on the current PG. We should identify when its > not the current PG and just reload the child PG. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13290) Dialog close on route navigation causes extra selection route to fire and browser history to be removed
[ https://issues.apache.org/jira/browse/NIFI-13290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13290: --- Status: Patch Available (was: In Progress) > Dialog close on route navigation causes extra selection route to fire and > browser history to be removed > --- > > Key: NIFI-13290 > URL: https://issues.apache.org/jira/browse/NIFI-13290 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan > Assignee: Matt Gilman >Priority: Major > Attachments: Kapture 2024-05-22 at 17.24.17.gif, example2.gif > > Time Spent: 10m > Remaining Estimate: 0h > > https://github.com/apache/nifi/pull/8859#discussion_r1612046025 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13286) Empty All Queues issues
[ https://issues.apache.org/jira/browse/NIFI-13286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13286: -- Assignee: Matt Gilman > Empty All Queues issues > --- > > Key: NIFI-13286 > URL: https://issues.apache.org/jira/browse/NIFI-13286 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > > Empty All Queues should conditionally reload the current PG or the selected > child PG depending on the subject of the action. Currently, the action > assumes it's being executed on the current PG. We should identify when its > not the current PG and just reload the child PG. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13290) Dialog close on route navigation causes extra selection route to fire and browser history to be removed
[ https://issues.apache.org/jira/browse/NIFI-13290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13290: -- Assignee: Matt Gilman > Dialog close on route navigation causes extra selection route to fire and > browser history to be removed > --- > > Key: NIFI-13290 > URL: https://issues.apache.org/jira/browse/NIFI-13290 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan > Assignee: Matt Gilman >Priority: Major > Attachments: Kapture 2024-05-22 at 17.24.17.gif, example2.gif > > > https://github.com/apache/nifi/pull/8859#discussion_r1612046025 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13289) Add tooltip to NewCanvas item
[ https://issues.apache.org/jira/browse/NIFI-13289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13289: --- Attachment: Screenshot 2024-05-23 at 2.36.55 PM.png > Add tooltip to NewCanvas item > - > > Key: NIFI-13289 > URL: https://issues.apache.org/jira/browse/NIFI-13289 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman >Priority: Major > Attachments: Screenshot 2024-05-23 at 2.36.55 PM.png > > > Old NiFi UI had tooltips for the new canvas items in the top bar. These are > currently missing in the new UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13289) Add tooltip to NewCanvas item
Matt Gilman created NIFI-13289: -- Summary: Add tooltip to NewCanvas item Key: NIFI-13289 URL: https://issues.apache.org/jira/browse/NIFI-13289 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Old NiFi UI had tooltips for the new canvas items in the top bar. These are currently missing in the new UI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13245) Provenance Event dialog overflow issues
[ https://issues.apache.org/jira/browse/NIFI-13245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13245: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Provenance Event dialog overflow issues > --- > > Key: NIFI-13245 > URL: https://issues.apache.org/jira/browse/NIFI-13245 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Fix For: 2.0.0-M4 > > Attachments: Screenshot 2024-05-15 at 10.18.51 AM.png > > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13207) Page header padding/spacing
[ https://issues.apache.org/jira/browse/NIFI-13207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13207: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Page header padding/spacing > --- > > Key: NIFI-13207 > URL: https://issues.apache.org/jira/browse/NIFI-13207 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Fix For: 2.0.0-M4 > > Attachments: Screenshot 2024-05-09 at 8.04.12 PM.png, Screenshot > 2024-05-09 at 8.04.20 PM.png, Screenshot 2024-05-09 at 8.04.30 PM.png, > Screenshot 2024-05-09 at 8.04.40 PM.png, Screenshot 2024-05-09 at 8.04.50 > PM.png, Screenshot 2024-05-09 at 8.05.02 PM.png, Screenshot 2024-05-09 at > 8.05.10 PM.png, Screenshot 2024-05-09 at 8.05.26 PM.png, Screenshot > 2024-05-09 at 8.05.33 PM.png > > Time Spent: 4h 40m > Remaining Estimate: 0h > > The various page header titles have various spacing padding: -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12967) Improve navigation to/from Canvas
[ https://issues.apache.org/jira/browse/NIFI-12967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17848966#comment-17848966 ] Matt Gilman commented on NIFI-12967: Also added back actions for * Go To Service (not from a Property reference) * Back from Service Listing * Back to Connection from Queue Listing * Back to Queue Listing from Provenance > Improve navigation to/from Canvas > - > > Key: NIFI-12967 > URL: https://issues.apache.org/jira/browse/NIFI-12967 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > > When leaving the Canvas (ie listing queue, viewing documentation, etc) the UI > should offer a more intuitive means to navigate back to where they were > before. Currently they must use the Global menu or click on the logo in the > header. However, these options are not necessarily obvious at first. The > browser back button also works but the UI should probably offer some in the > application. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13270) Selected tab is not saved
[ https://issues.apache.org/jira/browse/NIFI-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13270: --- Parent: NIFI-12400 Issue Type: Sub-task (was: Improvement) > Selected tab is not saved > - > > Key: NIFI-13270 > URL: https://issues.apache.org/jira/browse/NIFI-13270 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Julien G. >Priority: Major > > In a component such as a processor, when we select the Properties tab, the > selection was saved in the previous UI, so when we switch to another > processor, we don't need to select the tab again. In the new UI, we have to > select it again each time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13269) Parameter reference list is randomly ordered or not ordered
[ https://issues.apache.org/jira/browse/NIFI-13269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13269: --- Parent: NIFI-12400 Issue Type: Sub-task (was: Improvement) > Parameter reference list is randomly ordered or not ordered > --- > > Key: NIFI-13269 > URL: https://issues.apache.org/jira/browse/NIFI-13269 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Julien G. >Priority: Major > Attachments: Screenshot 2024-05-22 at 3.49.48 PM.png, > image-2024-05-21-11-04-26-571.png > > > When referencing a parameter in a Controller Service, a list of the availabe > parameter is displayed. > In the new UI, the list is randomly ordered or not ordered at all. > !image-2024-05-21-11-04-26-571.png|thumbnail! > It makes it hard to find a parameter. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13286) Empty All Queues issues
Matt Gilman created NIFI-13286: -- Summary: Empty All Queues issues Key: NIFI-13286 URL: https://issues.apache.org/jira/browse/NIFI-13286 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Empty All Queues should conditionally reload the current PG or the selected child PG depending on the subject of the action. Currently, the action assumes it's being executed on the current PG. We should identify when its not the current PG and just reload the child PG. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13285) Fit on Enter PG
Matt Gilman created NIFI-13285: -- Summary: Fit on Enter PG Key: NIFI-13285 URL: https://issues.apache.org/jira/browse/NIFI-13285 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman When navigating into a PG where there is no saved viewport position we should consider executing a fit action so that flow is shown centered on the canvas. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13284) Consider filtering current-canvas-route
Matt Gilman created NIFI-13284: -- Summary: Consider filtering current-canvas-route Key: NIFI-13284 URL: https://issues.apache.org/jira/browse/NIFI-13284 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Currently, the canvas tracks the current route so the user can be returned to where they were when returning to the canvas. We should consider filtering out any `edit` routes so that the user is returned to the place in the canvas rather then in an Edit dialog. Since dialogs are only and must be closed prior to using most navigation controls this won't happen regularly. However a user routes through a Go To command it will. By filtering out `edit` routes, it may be less confusing. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13247) Property Verification
[ https://issues.apache.org/jira/browse/NIFI-13247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13247: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Property Verification > - > > Key: NIFI-13247 > URL: https://issues.apache.org/jira/browse/NIFI-13247 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Fix For: 2.0.0-M4 > > Time Spent: 1h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-13277) Compact the main menu
[ https://issues.apache.org/jira/browse/NIFI-13277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-13277. Fix Version/s: 2.0.0-M4 Resolution: Fixed > Compact the main menu > - > > Key: NIFI-13277 > URL: https://issues.apache.org/jira/browse/NIFI-13277 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Fix For: 2.0.0-M4 > > Attachments: Screenshot 2024-05-21 at 1.05.17 PM.png, > image-2024-05-21-13-05-27-035.png > > Time Spent: 0.5h > Remaining Estimate: 0h > > The main menu has much padding. it makes it so large that on smaller > resolutions the whole menu doesn't fit > !image-2024-05-21-13-05-27-035.png|width=868,height=508! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13275) Remove web.xml from nifi-web-frontend
[ https://issues.apache.org/jira/browse/NIFI-13275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13275: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Remove web.xml from nifi-web-frontend > - > > Key: NIFI-13275 > URL: https://issues.apache.org/jira/browse/NIFI-13275 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > Fix For: 2.0.0-M4 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Following recent changes in nifi-web-frontend to remove the need for Servlet > Filters, the Servlet configuration in web.xml is no longer needed. With the > frontend code relying exclusively on REST API calls to nifi-web-api, the > web.xml configuration and nifi-web-utils dependencies are no longer required. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13278) Fix license file exclusion
[ https://issues.apache.org/jira/browse/NIFI-13278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13278: --- Status: Patch Available (was: In Progress) > Fix license file exclusion > -- > > Key: NIFI-13278 > URL: https://issues.apache.org/jira/browse/NIFI-13278 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Changes introduced in NIFI-12902 inadvertently excluded the > 3rdpartylicenses.txt file from being included in the resulting artifact. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13278) Fix license file exclusion
Matt Gilman created NIFI-13278: -- Summary: Fix license file exclusion Key: NIFI-13278 URL: https://issues.apache.org/jira/browse/NIFI-13278 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Changes introduced in NIFI-12902 inadvertently excluded the 3rdpartylicenses.txt file from being included in the resulting artifact. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12967) Improve navigation to/from Canvas
[ https://issues.apache.org/jira/browse/NIFI-12967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12967: --- Status: Patch Available (was: In Progress) > Improve navigation to/from Canvas > - > > Key: NIFI-12967 > URL: https://issues.apache.org/jira/browse/NIFI-12967 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When leaving the Canvas (ie listing queue, viewing documentation, etc) the UI > should offer a more intuitive means to navigate back to where they were > before. Currently they must use the Global menu or click on the logo in the > header. However, these options are not necessarily obvious at first. The > browser back button also works but the UI should probably offer some in the > application. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12967) Improve navigation to/from Canvas
[ https://issues.apache.org/jira/browse/NIFI-12967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847525#comment-17847525 ] Matt Gilman commented on NIFI-12967: This issue is not specific to navigating to/from the canvas. It applies to anytime we navigate from one thing to another where there is an expectation to return back to where the user was previously. * From any component (Processor/Service/Reporting Task/Parameter Context/etc) -> Manage Access Policies * From any component (Processor/Service/Reporting Task/etc) -> Controller Service * From any component (Processor/Service) -> Parameter Context * From any component (Processor/Service/Reporting Task/etc) -> Documentation * From any component (Processor/Service/Reporting Task/etc) -> Advanced UI * From Processor -> Provenance * From Process Group -> Parameters > Improve navigation to/from Canvas > - > > Key: NIFI-12967 > URL: https://issues.apache.org/jira/browse/NIFI-12967 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > When leaving the Canvas (ie listing queue, viewing documentation, etc) the UI > should offer a more intuitive means to navigate back to where they were > before. Currently they must use the Global menu or click on the logo in the > header. However, these options are not necessarily obvious at first. The > browser back button also works but the UI should probably offer some in the > application. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12967) Improve navigation to/from Canvas
[ https://issues.apache.org/jira/browse/NIFI-12967?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-12967: -- Assignee: Matt Gilman > Improve navigation to/from Canvas > - > > Key: NIFI-12967 > URL: https://issues.apache.org/jira/browse/NIFI-12967 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > > When leaving the Canvas (ie listing queue, viewing documentation, etc) the UI > should offer a more intuitive means to navigate back to where they were > before. Currently they must use the Global menu or click on the logo in the > header. However, these options are not necessarily obvious at first. The > browser back button also works but the UI should probably offer some in the > application. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13260) Selected canvas component which has color applied does not show the correct border
[ https://issues.apache.org/jira/browse/NIFI-13260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13260: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Selected canvas component which has color applied does not show the correct > border > -- > > Key: NIFI-13260 > URL: https://issues.apache.org/jira/browse/NIFI-13260 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Fix For: 2.0.0-M4 > > Attachments: image (4).png, image (5).png > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13232) Add REST API Resource for Authentication Configuration
[ https://issues.apache.org/jira/browse/NIFI-13232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13232: --- Fix Version/s: 2.0.0-M4 Resolution: Fixed Status: Resolved (was: Patch Available) > Add REST API Resource for Authentication Configuration > -- > > Key: NIFI-13232 > URL: https://issues.apache.org/jira/browse/NIFI-13232 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M4 > > Time Spent: 1h > Remaining Estimate: 0h > > The NiFi user interface applications include Servlet Filters to handle Login > and Logout redirection based on the configured authentication strategy. > Rather than continuing to maintain these filters, a new REST API resource > should be created to provide login and logout URLs based on application > configuration. The response should also indicate whether the system supports > login and logout operations so that the user interface can present the > appropriate forms and links according to the current system configuration. > Implementing this new REST API should support the removal of the Login and > Logout filters from the new user interface, simplifying the build and > deployment process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-13244) Paste location seems to be inconsistent
[ https://issues.apache.org/jira/browse/NIFI-13244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-13244. Resolution: Not A Problem The paste location currently works as designed. The paste location is based on the current position of the mouse when the user selects the Paste option from the context menu. We could consider alternatives (like the position of the context menu) if desired. > Paste location seems to be inconsistent > --- > > Key: NIFI-13244 > URL: https://issues.apache.org/jira/browse/NIFI-13244 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Priority: Major > Attachments: image-2024-05-15-10-14-52-757.png > > > !image-2024-05-15-10-14-52-757.png|width=809,height=359! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12968) Simplify login sequence
[ https://issues.apache.org/jira/browse/NIFI-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12968: --- Status: Patch Available (was: Reopened) > Simplify login sequence > --- > > Key: NIFI-12968 > URL: https://issues.apache.org/jira/browse/NIFI-12968 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Simply the login sequence for NiFi 2.0.0. > * Remove usage of Access-Token-Expiration > * No longer attempt SPNEGO auth > * Leverage authentication configuration to drive log in/out URIs > * Remove Login/Logout servlet filters > * Remove usage of access configuration and access status -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12968) Simplify login sequence
[ https://issues.apache.org/jira/browse/NIFI-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12968: --- Description: Simply the login sequence for NiFi 2.0.0. * Remove usage of Access-Token-Expiration * No longer attempt SPNEGO auth * Leverage authentication configuration to drive log in/out URIs * Remove Login/Logout servlet filters * Remove usage of access configuration and access status was: Simply the login sequence for NiFi 2.0.0. * Remove usage of Access-Token-Expiration * No longer attempt SPNEGO auth * Leverage authentication configuration to drive log in/out URIs * Remove usage of access configuration and access status > Simplify login sequence > --- > > Key: NIFI-12968 > URL: https://issues.apache.org/jira/browse/NIFI-12968 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > > Simply the login sequence for NiFi 2.0.0. > * Remove usage of Access-Token-Expiration > * No longer attempt SPNEGO auth > * Leverage authentication configuration to drive log in/out URIs > * Remove Login/Logout servlet filters > * Remove usage of access configuration and access status -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12968) Simplify login sequence
[ https://issues.apache.org/jira/browse/NIFI-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12968: --- Description: Simply the login sequence for NiFi 2.0.0. * Remove usage of Access-Token-Expiration * No longer attempt SPNEGO auth * Leverage authentication configuration to drive log in/out URIs * Remove usage of access configuration and access status was:Ensure the updated UI is handling token refresh appropriately and that the current token expiration is properly tracked to sure the user doesn't incorrectly see a message about the session ending. > Simplify login sequence > --- > > Key: NIFI-12968 > URL: https://issues.apache.org/jira/browse/NIFI-12968 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > > Simply the login sequence for NiFi 2.0.0. > * Remove usage of Access-Token-Expiration > * No longer attempt SPNEGO auth > * Leverage authentication configuration to drive log in/out URIs > * Remove usage of access configuration and access status -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12968) Simplify login sequence
[ https://issues.apache.org/jira/browse/NIFI-12968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12968: --- Summary: Simplify login sequence (was: Refresh token handling and keeping current token expiration) > Simplify login sequence > --- > > Key: NIFI-12968 > URL: https://issues.apache.org/jira/browse/NIFI-12968 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > > Ensure the updated UI is handling token refresh appropriately and that the > current token expiration is properly tracked to sure the user doesn't > incorrectly see a message about the session ending. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13236) Downloading Content with Non-ASCII Filenames Cause Exceptions with HTTP/2
[
https://issues.apache.org/jira/browse/NIFI-13236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-13236:
---
Fix Version/s: 2.0.0-M4
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Downloading Content with Non-ASCII Filenames Cause Exceptions with HTTP/2
> -
>
> Key: NIFI-13236
> URL: https://issues.apache.org/jira/browse/NIFI-13236
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 2.0.0-M2
> Reporter: Matt Gilman
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0-M4
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When attempting to view or download content the flowfile's filename (from the
> filename attribute) is used as the proposed downloaded filename. These
> endpoints support gzip encoding. If the filename contains characters are
> invalid VCHAR based on RFC9110, the endpoint fails with a connection error.
> The log contains the following exception.
>
> {noformat}
> 2024-05-14 14:52:40,290 ERROR [NiFi Web Server-138]
> o.g.j.server.ServerRuntime$Responder An I/O error has occurred while writing
> a response message entity to the container output stream.
> org.glassfish.jersey.server.internal.process.MappableException:
> java.io.IOException:
> org.eclipse.jetty.http2.hpack.HpackException$SessionException: Could not
> hpack encode HTTP/2.0{s=200,h=11,cl=-1}
> at
> org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundWriteTo(MappableExceptionWrapperInterceptor.java:67)
> at
> org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:139)
> at
> org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1116)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:678)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:387)
> at
> org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:377)
> at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:266)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
> at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
> at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
> at
> org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:266)
> at
> org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:242)
> at
> org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:697)
> at
> org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:394)
> at
> org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:358)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:312)
> at
> org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:205)
> at
> org.eclipse.jetty.ee10.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1379)
> at
> org.eclipse.jetty.ee10.servlet.ServletHolder.handle(ServletHolder.java:736)
> at
> org.eclipse.jetty.ee10.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1614)
> at
> org.springframework.security.web.FilterChainProxy.lambda$doFilterInternal$3(FilterChainProxy.java:231)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:365)
> at
> org.springframework.security.web.access.intercept.AuthorizationFilter.doFilter(AuthorizationFilter.java:100)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:126)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:120)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
> at
> org.apache.nifi.web.security.log.AuthenticationUserFilter.doFilterI
[jira] [Created] (NIFI-13236) Issue when viewing and downloading content
Matt Gilman created NIFI-13236:
--
Summary: Issue when viewing and downloading content
Key: NIFI-13236
URL: https://issues.apache.org/jira/browse/NIFI-13236
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Reporter: Matt Gilman
When attempting to view or download content the flowfile's filename (from the
filename attribute) is used as the proposed downloaded filename. These
endpoints support gzip encoding. If the filename contains characters are
invalid VCHAR based on RFC9110, the endpoint fails with a connection error. The
log contains the following exception.
{noformat}
2024-05-14 14:52:40,290 ERROR [NiFi Web Server-138]
o.g.j.server.ServerRuntime$Responder An I/O error has occurred while writing a
response message entity to the container output stream.
org.glassfish.jersey.server.internal.process.MappableException:
java.io.IOException:
org.eclipse.jetty.http2.hpack.HpackException$SessionException: Could not hpack
encode HTTP/2.0{s=200,h=11,cl=-1}
at
org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundWriteTo(MappableExceptionWrapperInterceptor.java:67)
at
org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:139)
at
org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1116)
at
org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:678)
at
org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:387)
at
org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:377)
at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:266)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
at
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:266)
at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:242)
at
org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:697)
at
org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:394)
at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:358)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:312)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:205)
at
org.eclipse.jetty.ee10.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1379)
at
org.eclipse.jetty.ee10.servlet.ServletHolder.handle(ServletHolder.java:736)
at
org.eclipse.jetty.ee10.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1614)
at
org.springframework.security.web.FilterChainProxy.lambda$doFilterInternal$3(FilterChainProxy.java:231)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:365)
at
org.springframework.security.web.access.intercept.AuthorizationFilter.doFilter(AuthorizationFilter.java:100)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
at
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:126)
at
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:120)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
at
org.apache.nifi.web.security.log.AuthenticationUserFilter.doFilterInternal(AuthenticationUserFilter.java:57)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:116)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
at
org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:100)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374)
at
org.springframework.security.oauth2.server.resource.web.authentication.BearerTokenAuthenticationFilter.doFilterInternal(BearerTokenAuthenticationFilter.java:145)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:116)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:374
[jira] [Updated] (NIFI-13228) Jolt Transform UI uses incorrect property names
[ https://issues.apache.org/jira/browse/NIFI-13228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13228: --- Status: Patch Available (was: In Progress) > Jolt Transform UI uses incorrect property names > --- > > Key: NIFI-13228 > URL: https://issues.apache.org/jira/browse/NIFI-13228 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > NIFI-12554 introducing a breaking change with the property names used by > JoltTransformJSON. The existing custom UI saves the transform and > specification into properties under the previous name. As a result, the > values are stored in dynamic properties. This custom UI needs to be updated > to leverage the new/updated Property names. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13211) Decouple UIs from old NiFi UI
[ https://issues.apache.org/jira/browse/NIFI-13211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13211: --- Status: Patch Available (was: In Progress) > Decouple UIs from old NiFi UI > - > > Key: NIFI-13211 > URL: https://issues.apache.org/jira/browse/NIFI-13211 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > NiFi is comprised of numerous UIs that all get deployed at start up. These > UIs piggybacked on some shared stylesheets, components, and dependencies by > directly loading them through a relative path. In preparation for moving away > from the existing UI, these UIs are being updated to bundle these items > directly. In time, these UIs will all be modernized as well so this is just a > transitional step in that process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13211) Decouple UIs from old NiFi UI
[ https://issues.apache.org/jira/browse/NIFI-13211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13211: --- Description: NiFi is comprised of numerous UIs that all get deployed at start up. These UIs piggybacked on some shared stylesheets, components, and dependencies by directly loading them through a relative path. In preparation for moving away from the existing UI, these UIs are being updated to bundle these items directly. In time, these UIs will all be modernized as well so this is just a transitional step in that process. > Decouple UIs from old NiFi UI > - > > Key: NIFI-13211 > URL: https://issues.apache.org/jira/browse/NIFI-13211 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > NiFi is comprised of numerous UIs that all get deployed at start up. These > UIs piggybacked on some shared stylesheets, components, and dependencies by > directly loading them through a relative path. In preparation for moving away > from the existing UI, these UIs are being updated to bundle these items > directly. In time, these UIs will all be modernized as well so this is just a > transitional step in that process. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13211) Decouple UIs from old NiFi UI
[ https://issues.apache.org/jira/browse/NIFI-13211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13211: --- Summary: Decouple UIs from old NiFi UI (was: Remove dataviewer dependencies on old UI) > Decouple UIs from old NiFi UI > - > > Key: NIFI-13211 > URL: https://issues.apache.org/jira/browse/NIFI-13211 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13228) Jolt Transform UI uses incorrect property names
Matt Gilman created NIFI-13228: -- Summary: Jolt Transform UI uses incorrect property names Key: NIFI-13228 URL: https://issues.apache.org/jira/browse/NIFI-13228 Project: Apache NiFi Issue Type: Bug Components: Extensions Reporter: Matt Gilman Assignee: Matt Gilman NIFI-12554 introducing a breaking change with the property names used by JoltTransformJSON. The existing custom UI saves the transform and specification into properties under the previous name. As a result, the values are stored in dynamic properties. This custom UI needs to be updated to leverage the new/updated Property names. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13153) [BUG] processors with long names cause overflow issues in dialogs
[ https://issues.apache.org/jira/browse/NIFI-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13153: --- Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > [BUG] processors with long names cause overflow issues in dialogs > - > > Key: NIFI-13153 > URL: https://issues.apache.org/jira/browse/NIFI-13153 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Fix For: 2.0.0-M3 > > Attachments: Screenshot 2024-05-06 at 1.46.25 PM.png, Screenshot > 2024-05-06 at 1.46.38 PM.png > > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13211) Remove dataviewer dependencies on old UI
Matt Gilman created NIFI-13211: -- Summary: Remove dataviewer dependencies on old UI Key: NIFI-13211 URL: https://issues.apache.org/jira/browse/NIFI-13211 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13204) Enable/Disable All Controller Services
[ https://issues.apache.org/jira/browse/NIFI-13204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13204: --- Status: Patch Available (was: Open) > Enable/Disable All Controller Services > -- > > Key: NIFI-13204 > URL: https://issues.apache.org/jira/browse/NIFI-13204 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13204) Enable/Disable All Controller Services
Matt Gilman created NIFI-13204: -- Summary: Enable/Disable All Controller Services Key: NIFI-13204 URL: https://issues.apache.org/jira/browse/NIFI-13204 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13060) UI - property table property column ellipsis
[ https://issues.apache.org/jira/browse/NIFI-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13060: --- Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > UI - property table property column ellipsis > > > Key: NIFI-13060 > URL: https://issues.apache.org/jira/browse/NIFI-13060 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan > Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0-M3 > > Attachments: Screenshot 2024-04-16 at 3.49.44 PM.png > > Time Spent: 20m > Remaining Estimate: 0h > > It can happen that a really long property name is displayed in a property > table. When this happens the ellipsis is not properly applied to the text. > !Screenshot 2024-04-16 at 3.49.44 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12537) *** Add pagination (NIFI-12552) *** Support Processor Details dialog *** Support Connection Details dialog * Counters (NIFI-12415) ** Counter table has extra unnecessary can modify check (NIFI-12948) * Bulletin Board (NIFI-12560) * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) ** Clustering (NIFI-12807) * Configure Reporting Task (NIFI-12563) * Flow Analysis Rules (NIFI-12588) * Registry Clients (NIFI-12486) * Import from Registry (NIFI-12734) * Parameter Providers (NIFI-12622) ** Fetch parameters from provider, map to parameter context (dialog) - (NIFI-12665) * Cluster ** Node table (Disconnect/Connect/Load Balance/Etc) (NIFI-13053) ** Status History - node specific values (NIFI-12848) * Flow Configuration History (NIFI-12754) ** ActionEntity.action should be optional (NIFI-12948) * Node Status History (NIFI-12553) * Status history for components from canvas context menu (NIFI-12553) * Users (NIFI-12543) ** Don't show users or groups in create/edit dialog is there are none (NIFI-12948) * Policies (NIFI-12548) ** Overridden policy Empty or Copy (NIFI-12679) ** Select Empty by default (NIFI-12948) * Help (NIFI-12795) * About (NIFI-13094) * Show Upstream/Downstream * Align (NIFI-13162) * Replay last event (NIFI-12445) * List Queue (NIFI-12589) ** Clustering (NIFI-12807) * Empty [all] Queue (NIFI-12604) * View Content (NIFI-12589 and NIFI-12445) * View State (NIFI-12611) ** Clustering (NIFI-13005) * Change Component Version (NIFI-13034) * Consider PG permissions in Toolbox (NIFI-12683) * PG Version (NIFI-12963 & NIFI-12995) ** Start (NIFI-12963) ** Commit (NIFI-12963) ** Force Commit (NIFI-12963) ** Show changes (NIFI-12995) ** Revert changes (NIFI-12995) ** Change Flow version (NIFI-12995) ** Stop (NIFI-12963) * Configure PG (NIFI-12417) * Configure Label (NIFI-13081) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs ** Disable and Configure * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) ** Fix issue with Property Editor width (NIFI-12547) ** Status Bar ** Stop and Configure ** Open Custom UI (NIFI-12958) ** Property History (NIFI-13047) ** Unable to re-add any removed Property (NIFI-12743) ** Shift-Enter new line when editing Property (NIFI-12743) * Property Verification * Terminate Threads (context menu) (NIFI-13068) * Enable/Disable (context menu/operate panel) (NIFI-13078) * More Details (Processor, Controller Service, Reporting Task) (NIFI-13062) * Download Flow (NIFI-13029) * Create RPG (NIFI-12758) * Configure RPG (NIFI-12774) * RPG Remote Ports (NIFI-12778) * RPG Go To (NIFI-12759) * RPG Refresh (NIFI-12761) * Color (context menu/operate panel) * Move to Front (NIFI-13044) * Copy/Paste (context menu/operate panel) (NIFI-13059) * Add/Update Info Icons in dialogs throughout the application (NIFI-13092) * Set viewport earlier when loading a Process Group (NIFI-12737) * Canvas global menu item should navigate user back to where they were on the canvas (NIFI-12737) * Better theme support (NIFI-12655) * Set up development/production environments files * Run unit tests are part of standard build (NIFI-12941) * Update all API calls to consider disconnect node confirmation (NIFI-13001) * Update API calls to use uiOnly flag (NIFI-12950) * Use polling interval from API * Load FlowConfiguration in guard (NIFI-12948) * Routing error handling (NIFI-13104) * General API response error handling ** Management CS (NIFI-12663) ** Canvas CS (NIFI-12684) ** Remainder of Settings (NIFI-12723) ** Counters (NIFI-12723) ** Bulletins (NIFI-12723) ** Flow Designer (NIFI-13100) ** Parameter Contexts (NIFI-12937) ** Con
[jira] [Updated] (NIFI-13195) Cluster Request Replicator not handling header removal with HTTP/2
[
https://issues.apache.org/jira/browse/NIFI-13195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-13195:
---
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Cluster Request Replicator not handling header removal with HTTP/2
> --
>
> Key: NIFI-13195
> URL: https://issues.apache.org/jira/browse/NIFI-13195
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Reporter: David Handermann
>Assignee: David Handermann
>Priority: Major
> Fix For: 2.0.0-M3
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The {{ThreadPoolRequestReplicator}} performs HTTP request replication between
> cluster nodes and includes several methods for removing headers that should
> not be passed in forwarded requests. When receiving requests over HTTP/1.1,
> header names can be capitalized, but over HTTP/2, header names are lowercase.
> The removal logic should be updated to handle header removal without
> depending on the protocol format of the header names.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13060) UI - property table property column ellipsis
[ https://issues.apache.org/jira/browse/NIFI-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13060: --- Status: Patch Available (was: Open) > UI - property table property column ellipsis > > > Key: NIFI-13060 > URL: https://issues.apache.org/jira/browse/NIFI-13060 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan > Assignee: Matt Gilman >Priority: Major > Attachments: Screenshot 2024-04-16 at 3.49.44 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > > It can happen that a really long property name is displayed in a property > table. When this happens the ellipsis is not properly applied to the text. > !Screenshot 2024-04-16 at 3.49.44 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13060) UI - property table property column ellipsis
[ https://issues.apache.org/jira/browse/NIFI-13060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13060: -- Assignee: Matt Gilman > UI - property table property column ellipsis > > > Key: NIFI-13060 > URL: https://issues.apache.org/jira/browse/NIFI-13060 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan > Assignee: Matt Gilman >Priority: Major > Attachments: Screenshot 2024-04-16 at 3.49.44 PM.png > > > It can happen that a really long property name is displayed in a property > table. When this happens the ellipsis is not properly applied to the text. > !Screenshot 2024-04-16 at 3.49.44 PM.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-13197) Clicking outside of dialog cancels edit
Matt Gilman created NIFI-13197: -- Summary: Clicking outside of dialog cancels edit Key: NIFI-13197 URL: https://issues.apache.org/jira/browse/NIFI-13197 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Default behavior of dialog is to support closing when the user clicks off. Incidental clicks could result in the loss of unsaved changes. We should consider * Always preventing closing * Only prevent closing for Edit dialogs * Only prevent closing when dialogs contain a dirty form -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-13158) Support keyboard shortcuts on the canvas
[ https://issues.apache.org/jira/browse/NIFI-13158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-13158. Fix Version/s: 2.0.0-M3 Resolution: Fixed > Support keyboard shortcuts on the canvas > > > Key: NIFI-13158 > URL: https://issues.apache.org/jira/browse/NIFI-13158 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 40m > Remaining Estimate: 0h > > CTRL+R -> reload canvas > CTRL+A -> select all > CTRL+C -> copy > CTRL+V -> paste > Backspace/Delete -> delete > ESC -> leave group -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13176) Relax the minimum scale on the canvas
[ https://issues.apache.org/jira/browse/NIFI-13176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13176: --- Status: Patch Available (was: In Progress) > Relax the minimum scale on the canvas > - > > Key: NIFI-13176 > URL: https://issues.apache.org/jira/browse/NIFI-13176 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-13176) Relax the minimum scale on the canvas
[ https://issues.apache.org/jira/browse/NIFI-13176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-13176: -- Assignee: Matt Gilman > Relax the minimum scale on the canvas > - > > Key: NIFI-13176 > URL: https://issues.apache.org/jira/browse/NIFI-13176 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13175) Double scroll bar in dialogs on smaller screen
[ https://issues.apache.org/jira/browse/NIFI-13175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13175: --- Status: Patch Available (was: In Progress) > Double scroll bar in dialogs on smaller screen > -- > > Key: NIFI-13175 > URL: https://issues.apache.org/jira/browse/NIFI-13175 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI > Reporter: Matt Gilman > Assignee: Matt Gilman >Priority: Major > Attachments: Screenshot 2024-05-07 at 4.21.07 PM.png > > Time Spent: 10m > Remaining Estimate: 0h > > For smaller screen sizes there is not enough vertical space to render the > dialog in it's entirety. As a result the user ends up seeing a double scroll > bar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-13162) Align components
[ https://issues.apache.org/jira/browse/NIFI-13162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-13162: --- Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Align components > > > Key: NIFI-13162 > URL: https://issues.apache.org/jira/browse/NIFI-13162 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Scott Aslan >Assignee: Scott Aslan >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 1h 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
