[jira] [Created] (NIFI-6690) Limit GoTo parameter action to parameters that exist in the active context.
Robert Fellows created NIFI-6690:
Summary: Limit GoTo parameter action to parameters that exist in
the active context.
Key: NIFI-6690
URL: https://issues.apache.org/jira/browse/NIFI-6690
Project: Apache NiFi
Issue Type: Improvement
Components: Core UI
Affects Versions: 1.10.0
Reporter: Robert Fellows
Currently, on the processor controller-service configuration dialogs, if a
value of a property matches the pattern of what a parameter reference looks
like *[1]*, the action to goto that parameter is available. However, if that
parameter does not exist in the parameter context, it can't find it to
highlight it in the table.
The goto action should only be available if the parameter reference matches a
parameter that already exists in the parameter context.
{{*[1]* #\{param name}}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (NIFI-6671) UI:Parameters listed in "Reference parameter..." drop-down not listed alphabetically
[ https://issues.apache.org/jira/browse/NIFI-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6671: - Status: Patch Available (was: In Progress) > UI:Parameters listed in "Reference parameter..." drop-down not listed > alphabetically > > > Key: NIFI-6671 > URL: https://issues.apache.org/jira/browse/NIFI-6671 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Andrew Lim >Assignee: Robert Fellows >Priority: Major > Attachments: alphabetical_order.png, wrong-order.png > > Time Spent: 10m > Remaining Estimate: 0h > > I created a Parameter Context and then added three parameters in this order: > level1 > level2 > level3 > But these parameters are listed in the following order when I try to select > them for a property value: > level1 > level3 > level2 > > See attached screenshots. If not easily reproducible, I can attach a video of > my exact steps. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFI-6671) UI:Parameters listed in "Reference parameter..." drop-down not listed alphabetically
[ https://issues.apache.org/jira/browse/NIFI-6671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6671: Assignee: Robert Fellows > UI:Parameters listed in "Reference parameter..." drop-down not listed > alphabetically > > > Key: NIFI-6671 > URL: https://issues.apache.org/jira/browse/NIFI-6671 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Andrew Lim >Assignee: Robert Fellows >Priority: Major > Attachments: alphabetical_order.png, wrong-order.png > > > I created a Parameter Context and then added three parameters in this order: > level1 > level2 > level3 > But these parameters are listed in the following order when I try to select > them for a property value: > level1 > level3 > level2 > > See attached screenshots. If not easily reproducible, I can attach a video of > my exact steps. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6659) Create new parameter context option from process group config opens the new param context dialog in a read-only state.
[ https://issues.apache.org/jira/browse/NIFI-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6659: - Status: Patch Available (was: In Progress) > Create new parameter context option from process group config opens the new > param context dialog in a read-only state. > -- > > Key: NIFI-6659 > URL: https://issues.apache.org/jira/browse/NIFI-6659 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6659) Create new parameter context option from process group config opens the new param context dialog in a read-only state.
Robert Fellows created NIFI-6659: Summary: Create new parameter context option from process group config opens the new param context dialog in a read-only state. Key: NIFI-6659 URL: https://issues.apache.org/jira/browse/NIFI-6659 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Robert Fellows Assignee: Robert Fellows -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6381) Make Parameters and Parameter Contexts searchable in UI
[ https://issues.apache.org/jira/browse/NIFI-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6381: - Status: Patch Available (was: In Progress) > Make Parameters and Parameter Contexts searchable in UI > --- > > Key: NIFI-6381 > URL: https://issues.apache.org/jira/browse/NIFI-6381 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework >Reporter: Mark Payne >Assignee: Robert Fellows >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFI-6381) Make Parameters and Parameter Contexts searchable in UI
[ https://issues.apache.org/jira/browse/NIFI-6381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6381: Assignee: Robert Fellows > Make Parameters and Parameter Contexts searchable in UI > --- > > Key: NIFI-6381 > URL: https://issues.apache.org/jira/browse/NIFI-6381 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework >Reporter: Mark Payne >Assignee: Robert Fellows >Priority: Minor > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFI-6634) UI - Indicate variable are no longer recommended and favor parameters
[ https://issues.apache.org/jira/browse/NIFI-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6634: Assignee: Robert Fellows > UI - Indicate variable are no longer recommended and favor parameters > - > > Key: NIFI-6634 > URL: https://issues.apache.org/jira/browse/NIFI-6634 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > > Variables less powerful than parameters. Specifically, they don't support > sensitive values. On the Variables dialog, this should be conveyed to the > user to help guide them to use parameters instead. > One suggestion for wording: > "Variables are still supported for compatibility purposes but they do not > allow the same power as Parameters such as support for sensitive parameters. > Variables will be removed in a later release so please change to using > parameters." -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFI-6630) Add a "Go To" button in property dialog that goes to a referenced parameter
[ https://issues.apache.org/jira/browse/NIFI-6630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6630: Assignee: Robert Fellows > Add a "Go To" button in property dialog that goes to a referenced parameter > --- > > Key: NIFI-6630 > URL: https://issues.apache.org/jira/browse/NIFI-6630 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Mark Payne >Assignee: Robert Fellows >Priority: Minor > > We now have the ability to "promote" a property value to a Parameter, which > is extremely helpful. Once a property is referencing a Parameter, though, it > would be helpful to be able to click a button to jump to the referenced > parameter in the Parameter Context. If the property references multiple > parameters, perhaps it should just jump to the first parameter referenced. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6644) UI: Account for user permissions when showing the option to convert props to params
[ https://issues.apache.org/jira/browse/NIFI-6644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6644: - Status: Patch Available (was: In Progress) > UI: Account for user permissions when showing the option to convert props to > params > --- > > Key: NIFI-6644 > URL: https://issues.apache.org/jira/browse/NIFI-6644 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > A user that does not have write permissions to the appropriate parameter > context should not be able to convert a property to a parameter. The option > should not be available in the property table. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6644) UI: Account for user permissions when showing the option to convert props to params
Robert Fellows created NIFI-6644: Summary: UI: Account for user permissions when showing the option to convert props to params Key: NIFI-6644 URL: https://issues.apache.org/jira/browse/NIFI-6644 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Robert Fellows Assignee: Robert Fellows A user that does not have write permissions to the appropriate parameter context should not be able to convert a property to a parameter. The option should not be available in the property table. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6641) UI:Parameter Context dialog needs to support non-editable scenario
[ https://issues.apache.org/jira/browse/NIFI-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6641: - Status: Patch Available (was: In Progress) > UI:Parameter Context dialog needs to support non-editable scenario > -- > > Key: NIFI-6641 > URL: https://issues.apache.org/jira/browse/NIFI-6641 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Andrew Lim >Assignee: Robert Fellows >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > If a user can view but not modify Parameter Contexts, selecting "Parameter > Contexts" from the global menu appropriately does not allow any editing > capability, but the user is unable to see the parameters within the Parameter > Contexts. Need to enable this. > If a Parameter Context is assigned to a PG, the user can access the "Update > Parameter Context" dialog via the Parameters selection in the context menu. > On the Parameters tab, the Add, Edit and Delete buttons are all selectable. > The user can make numerous edits (add more parameters, etc.), only to get the > "Insufficient Permissions" dialog upon selecting Apply. We should only show a > Close button in this scenario. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFI-6641) UI:Parameter Context dialog needs to support non-editable scenario
[ https://issues.apache.org/jira/browse/NIFI-6641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6641: Assignee: Robert Fellows > UI:Parameter Context dialog needs to support non-editable scenario > -- > > Key: NIFI-6641 > URL: https://issues.apache.org/jira/browse/NIFI-6641 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Andrew Lim >Assignee: Robert Fellows >Priority: Major > > If a user can view but not modify Parameter Contexts, selecting "Parameter > Contexts" from the global menu appropriately does not allow any editing > capability, but the user is unable to see the parameters within the Parameter > Contexts. Need to enable this. > If a Parameter Context is assigned to a PG, the user can access the "Update > Parameter Context" dialog via the Parameters selection in the context menu. > On the Parameters tab, the Add, Edit and Delete buttons are all selectable. > The user can make numerous edits (add more parameters, etc.), only to get the > "Insufficient Permissions" dialog upon selecting Apply. We should only show a > Close button in this scenario. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6632) UI - Indicate to the user in the Add and Edit Parameter dialogs that the value field does not support EL or Param references
[ https://issues.apache.org/jira/browse/NIFI-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6632: - Status: Patch Available (was: In Progress) > UI - Indicate to the user in the Add and Edit Parameter dialogs that the > value field does not support EL or Param references > > > Key: NIFI-6632 > URL: https://issues.apache.org/jira/browse/NIFI-6632 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > To avoid confusion, the dialogs should indicate that the value field is > treated as a literal string and not evaluated as EL or a reference to another > parameter. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFI-6632) UI - Indicate to the user in the Add and Edit Parameter dialogs that the value field does not support EL or Param references
[ https://issues.apache.org/jira/browse/NIFI-6632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6632: Assignee: Robert Fellows > UI - Indicate to the user in the Add and Edit Parameter dialogs that the > value field does not support EL or Param references > > > Key: NIFI-6632 > URL: https://issues.apache.org/jira/browse/NIFI-6632 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > > To avoid confusion, the dialogs should indicate that the value field is > treated as a literal string and not evaluated as EL or a reference to another > parameter. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6637) UI - Display the parameter context UUID
[ https://issues.apache.org/jira/browse/NIFI-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6637: - Status: Patch Available (was: In Progress) > UI - Display the parameter context UUID > --- > > Key: NIFI-6637 > URL: https://issues.apache.org/jira/browse/NIFI-6637 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > It might be important for users to know the UUID of a parameter context when > adding access policies via Ranger. It should be displayed on the Edit > Parameter Context dialog and possibly in the parameter context list. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6623) Support linking to unauthorized components from referencing components
[ https://issues.apache.org/jira/browse/NIFI-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6623: - Resolution: Fixed Status: Resolved (was: Patch Available) > Support linking to unauthorized components from referencing components > -- > > Key: NIFI-6623 > URL: https://issues.apache.org/jira/browse/NIFI-6623 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > Initially the referencing components that are read-only do not indicate the > type of component that they are (processor/controller service) so linking to > the component is not straight forward. > Regardless of the read permission, the API should provide the type of > component it is. Then, the user interface can link to the proper place based > on that information. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFI-6637) UI - Display the parameter context UUID
[ https://issues.apache.org/jira/browse/NIFI-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6637: Assignee: Robert Fellows > UI - Display the parameter context UUID > --- > > Key: NIFI-6637 > URL: https://issues.apache.org/jira/browse/NIFI-6637 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > > It might be important for users to know the UUID of a parameter context when > adding access policies via Ranger. It should be displayed on the Edit > Parameter Context dialog and possibly in the parameter context list. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6637) UI - Display the parameter context UUID
Robert Fellows created NIFI-6637: Summary: UI - Display the parameter context UUID Key: NIFI-6637 URL: https://issues.apache.org/jira/browse/NIFI-6637 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Robert Fellows It might be important for users to know the UUID of a parameter context when adding access policies via Ranger. It should be displayed on the Edit Parameter Context dialog and possibly in the parameter context list. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6623) Support linking to unauthorized components from referencing components
[ https://issues.apache.org/jira/browse/NIFI-6623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6623: - Status: Patch Available (was: In Progress) > Support linking to unauthorized components from referencing components > -- > > Key: NIFI-6623 > URL: https://issues.apache.org/jira/browse/NIFI-6623 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > Time Spent: 1h > Remaining Estimate: 0h > > Initially the referencing components that are read-only do not indicate the > type of component that they are (processor/controller service) so linking to > the component is not straight forward. > Regardless of the read permission, the API should provide the type of > component it is. Then, the user interface can link to the proper place based > on that information. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6635) Allow users the ability to create parameters from existing variables
Robert Fellows created NIFI-6635: Summary: Allow users the ability to create parameters from existing variables Key: NIFI-6635 URL: https://issues.apache.org/jira/browse/NIFI-6635 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Robert Fellows As variables are being deprecated in favor of parameters, it would be very beneficial to provide something to ease the migration. Letting users create parameters for all existing variables would be a huge efficiency gain. Possibly add a button on the Variables dialog that would just create parameters named the same as the variables with the value and assign them to the current parameter context. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6634) UI - Indicate variable are no longer recommended and favor parameters
Robert Fellows created NIFI-6634: Summary: UI - Indicate variable are no longer recommended and favor parameters Key: NIFI-6634 URL: https://issues.apache.org/jira/browse/NIFI-6634 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Robert Fellows Variables less powerful than parameters. Specifically, they don't support sensitive values. On the Variables dialog, this should be conveyed to the user to help guide them to use parameters instead. One suggestion for wording: "Variables are still supported for compatibility purposes but they do not allow the same power as Parameters such as support for sensitive parameters. Variables will be removed in a later release so please change to using parameters." -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6633) Allow user to copy a parameter context
Robert Fellows created NIFI-6633: Summary: Allow user to copy a parameter context Key: NIFI-6633 URL: https://issues.apache.org/jira/browse/NIFI-6633 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Robert Fellows It would be nice to be able to copy/duplicate an existing parameter context. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6632) UI - Indicate to the user in the Add and Edit Parameter dialogs that the value field does not support EL or Param references
Robert Fellows created NIFI-6632: Summary: UI - Indicate to the user in the Add and Edit Parameter dialogs that the value field does not support EL or Param references Key: NIFI-6632 URL: https://issues.apache.org/jira/browse/NIFI-6632 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Robert Fellows To avoid confusion, the dialogs should indicate that the value field is treated as a literal string and not evaluated as EL or a reference to another parameter. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6623) Support linking to unauthorized components from referencing components
Robert Fellows created NIFI-6623: Summary: Support linking to unauthorized components from referencing components Key: NIFI-6623 URL: https://issues.apache.org/jira/browse/NIFI-6623 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Robert Fellows Assignee: Robert Fellows Initially the referencing components that are read-only do not indicate the type of component that they are (processor/controller service) so linking to the component is not straight forward. Regardless of the read permission, the API should provide the type of component it is. Then, the user interface can link to the proper place based on that information. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6602) Parameters: "Apply" button should be greyed out if no changes have been
[ https://issues.apache.org/jira/browse/NIFI-6602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6602: - Status: Patch Available (was: In Progress) > Parameters: "Apply" button should be greyed out if no changes have been > --- > > Key: NIFI-6602 > URL: https://issues.apache.org/jira/browse/NIFI-6602 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Andrew Lim >Assignee: Robert Fellows >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Open the Parameters Context window. Whether on the Settings tab or Parameters > tab, the "Apply" button is available for selection immediately even when no > edits have been made to apply. If selected, the window is closed which is > what the Cancel button is for. > > Noticed while testing the PR branch for NIFI-6282. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFI-6602) Parameters: "Apply" button should be greyed out if no changes have been
[ https://issues.apache.org/jira/browse/NIFI-6602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6602: Assignee: Robert Fellows > Parameters: "Apply" button should be greyed out if no changes have been > --- > > Key: NIFI-6602 > URL: https://issues.apache.org/jira/browse/NIFI-6602 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Andrew Lim >Assignee: Robert Fellows >Priority: Minor > > Open the Parameters Context window. Whether on the Settings tab or Parameters > tab, the "Apply" button is available for selection immediately even when no > edits have been made to apply. If selected, the window is closed which is > what the Cancel button is for. > > Noticed while testing the PR branch for NIFI-6282. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (NIFI-6607) UI: State of referencing processors in Parameter Context dialog do not update after "Apply"
[ https://issues.apache.org/jira/browse/NIFI-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16921429#comment-16921429 ] Robert Fellows commented on NIFI-6607: -- This actually seems to not be an issue with the UI. The response from the server still indicates that the validation errors are as they were prior to the update to the parameter context. > UI: State of referencing processors in Parameter Context dialog do not update > after "Apply" > --- > > Key: NIFI-6607 > URL: https://issues.apache.org/jira/browse/NIFI-6607 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Andrew Lim >Priority: Major > > Change a parameter in a parameter context and select "Apply". The state of > the referencing processors do not update. For example, if the referencing > processor is in Invalid state and I corrected the problem with the parameter, > the state will stay in invalid state but on the canvas it is no longer > invalid. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFI-6607) UI: State of referencing processors in Parameter Context dialog do not update after "Apply"
[ https://issues.apache.org/jira/browse/NIFI-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6607: Assignee: (was: Robert Fellows) > UI: State of referencing processors in Parameter Context dialog do not update > after "Apply" > --- > > Key: NIFI-6607 > URL: https://issues.apache.org/jira/browse/NIFI-6607 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Andrew Lim >Priority: Major > > Change a parameter in a parameter context and select "Apply". The state of > the referencing processors do not update. For example, if the referencing > processor is in Invalid state and I corrected the problem with the parameter, > the state will stay in invalid state but on the canvas it is no longer > invalid. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFI-6607) UI: State of referencing processors in Parameter Context dialog do not update after "Apply"
[ https://issues.apache.org/jira/browse/NIFI-6607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6607: Assignee: Robert Fellows > UI: State of referencing processors in Parameter Context dialog do not update > after "Apply" > --- > > Key: NIFI-6607 > URL: https://issues.apache.org/jira/browse/NIFI-6607 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Andrew Lim >Assignee: Robert Fellows >Priority: Major > > Change a parameter in a parameter context and select "Apply". The state of > the referencing processors do not update. For example, if the referencing > processor is in Invalid state and I corrected the problem with the parameter, > the state will stay in invalid state but on the canvas it is no longer > invalid. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6568) Surface time-to-back-pressure and initial predictions in the UI.
[ https://issues.apache.org/jira/browse/NIFI-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6568: - Resolution: Fixed Status: Resolved (was: Patch Available) > Surface time-to-back-pressure and initial predictions in the UI. > > > Key: NIFI-6568 > URL: https://issues.apache.org/jira/browse/NIFI-6568 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > Back pressure predictions should be made visible in the flow designer and in > the connection summary table. > * Add indicators on connection widgets for predicted count and size of > connection queues. > * Add prediction information on the tooltips for those queues > * Add time to back pressure prediction to the connection summary table. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6453) Support building nifi-fds on Windows
[ https://issues.apache.org/jira/browse/NIFI-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6453: - Status: Patch Available (was: In Progress) > Support building nifi-fds on Windows > > > Key: NIFI-6453 > URL: https://issues.apache.org/jira/browse/NIFI-6453 > Project: Apache NiFi > Issue Type: Improvement > Components: FDS >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The current build architecture depends on bash scripts, preventing it from > being run on Windows systems (without cygwin). The goal would be to make it > os-agnostic. > One potential approach would be to leverage node.js for the pieces that > currently require a bash script. This includes things like: > * copying files (can use [rimraf|https://www.npmjs.com/package/rimraf]) > * creating directories (can use [mkdirp|https://www.npmjs.com/package/mkdirp]) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6568) Surface time-to-back-pressure and initial predictions in the UI.
[ https://issues.apache.org/jira/browse/NIFI-6568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFI-6568: - Status: Patch Available (was: In Progress) > Surface time-to-back-pressure and initial predictions in the UI. > > > Key: NIFI-6568 > URL: https://issues.apache.org/jira/browse/NIFI-6568 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > > Back pressure predictions should be made visible in the flow designer and in > the connection summary table. > * Add indicators on connection widgets for predicted count and size of > connection queues. > * Add prediction information on the tooltips for those queues > * Add time to back pressure prediction to the connection summary table. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6568) Surface time-to-back-pressure and initial predictions in the UI.
Robert Fellows created NIFI-6568: Summary: Surface time-to-back-pressure and initial predictions in the UI. Key: NIFI-6568 URL: https://issues.apache.org/jira/browse/NIFI-6568 Project: Apache NiFi Issue Type: Sub-task Reporter: Robert Fellows Assignee: Robert Fellows Back pressure predictions should be made visible in the flow designer and in the connection summary table. * Add indicators on connection widgets for predicted count and size of connection queues. * Add prediction information on the tooltips for those queues * Add time to back pressure prediction to the connection summary table. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFIREG-304) UI - Sorting the grid-list expands the listed buckets
Robert Fellows created NIFIREG-304: -- Summary: UI - Sorting the grid-list expands the listed buckets Key: NIFIREG-304 URL: https://issues.apache.org/jira/browse/NIFIREG-304 Project: NiFi Registry Issue Type: Bug Reporter: Robert Fellows Attachments: sort expands list.mov When choosing a sort option from the dropdown, the resulting sorted items in the list are expanded. View the attached screen recording -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFIREG-302) Enable building with uncompressed javascript
[ https://issues.apache.org/jira/browse/NIFIREG-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFIREG-302: --- Description: There should be a profile or some build option that triggers the javascript frontend to not be compressed (actually compressed but WITH sourcemaps) when included in the final build. This is very key when building/debugging frontend code against a secured backend since the configuration of the webpack dev server for normal development is not capable (currently) of supporting secured, proxied requests to the backend. (was: There should be a profile or some build option that triggers the javascript frontend to NOT be compressed when included in the final build. This is very key when building/debugging frontend code against a secured backend since the configuration of the webpack dev server for normal development is not capable (currently) of supporting secured, proxied requests to the backend.) > Enable building with uncompressed javascript > > > Key: NIFIREG-302 > URL: https://issues.apache.org/jira/browse/NIFIREG-302 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > > There should be a profile or some build option that triggers the javascript > frontend to not be compressed (actually compressed but WITH sourcemaps) when > included in the final build. This is very key when building/debugging > frontend code against a secured backend since the configuration of the > webpack dev server for normal development is not capable (currently) of > supporting secured, proxied requests to the backend. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFIREG-302) Enable building with uncompressed javascript
Robert Fellows created NIFIREG-302: -- Summary: Enable building with uncompressed javascript Key: NIFIREG-302 URL: https://issues.apache.org/jira/browse/NIFIREG-302 Project: NiFi Registry Issue Type: Improvement Reporter: Robert Fellows Assignee: Robert Fellows There should be a profile or some build option that triggers the javascript frontend to NOT be compressed when included in the final build. This is very key when building/debugging frontend code against a secured backend since the configuration of the webpack dev server for normal development is not capable (currently) of supporting secured, proxied requests to the backend. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (NIFI-6506) UI - Allow property values to be converted into parameters
[ https://issues.apache.org/jira/browse/NIFI-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6506: Assignee: Robert Fellows > UI - Allow property values to be converted into parameters > -- > > Key: NIFI-6506 > URL: https://issues.apache.org/jira/browse/NIFI-6506 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Robert Fellows >Priority: Major > > We should provide actions on properties to allow their currently configured > values to be converted into a parameter reference. This action should result > in creating a new parameter. We should be able to utilize the existing new > parameter dialog and pre-populate the fields with the property name and > current property value. Once the new parameter is created, we should be able > to update the value of the property with a reference to the new parameter. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (NIFI-6474) FDS - Document required dependencies for upgrade when consuming app migrated to a new version
[ https://issues.apache.org/jira/browse/NIFI-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows resolved NIFI-6474. -- Resolution: Fixed > FDS - Document required dependencies for upgrade when consuming app migrated > to a new version > - > > Key: NIFI-6474 > URL: https://issues.apache.org/jira/browse/NIFI-6474 > Project: Apache NiFi > Issue Type: Task > Components: FDS >Reporter: Robert Fellows >Priority: Major > > Migrating from @nifi-fds/core 0.1.0 to 0.2.0 also requires consuming apps to > upgade to angular 8, rxjs 6, and others. This should be called out in the > README and/or the Wiki so alert consumers of this lib of the impact upgrading > might have on their application. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (NIFI-6474) FDS - Document required dependencies for upgrade when consuming app migrated to a new version
[ https://issues.apache.org/jira/browse/NIFI-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16895251#comment-16895251 ] Robert Fellows commented on NIFI-6474: -- This has been resolved in this commit: https://github.com/apache/nifi-fds/commit/0b2443fce830a69f45c2d096872f84871e814d17 > FDS - Document required dependencies for upgrade when consuming app migrated > to a new version > - > > Key: NIFI-6474 > URL: https://issues.apache.org/jira/browse/NIFI-6474 > Project: Apache NiFi > Issue Type: Task > Components: FDS >Reporter: Robert Fellows >Priority: Major > > Migrating from @nifi-fds/core 0.1.0 to 0.2.0 also requires consuming apps to > upgade to angular 8, rxjs 6, and others. This should be called out in the > README and/or the Wiki so alert consumers of this lib of the impact upgrading > might have on their application. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFIREG-297) Upgrade to latest LTS release of Node (and npm)
Robert Fellows created NIFIREG-297: -- Summary: Upgrade to latest LTS release of Node (and npm) Key: NIFIREG-297 URL: https://issues.apache.org/jira/browse/NIFIREG-297 Project: NiFi Registry Issue Type: Improvement Reporter: Robert Fellows nifi-registry currently requires node 8.10.0 and npm 5.6.0. The current LTS for node is v10 and based on the scheduled release, v12 will be in October of 2019. One driving factor behind this is to get to a version of npm that includes npm audit. npm v6+ includes it (which is packaged with Node v10). -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6494) Upgrade to latest LTS release of Node (and npm)
Robert Fellows created NIFI-6494: Summary: Upgrade to latest LTS release of Node (and npm) Key: NIFI-6494 URL: https://issues.apache.org/jira/browse/NIFI-6494 Project: Apache NiFi Issue Type: Improvement Components: FDS Reporter: Robert Fellows nifi-fds currently requires node 8.10.0 and npm 5.6.0. The current LTS for node is v10 and based on the scheduled release, v12 will be in October of 2019. One driving factor behind this is to get to a version of npm that includes npm audit. npm v6+ includes it (which is packaged with Node v10). -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6474) FDS - Document required dependencies for upgrade when consuming app migrated to a new version
Robert Fellows created NIFI-6474: Summary: FDS - Document required dependencies for upgrade when consuming app migrated to a new version Key: NIFI-6474 URL: https://issues.apache.org/jira/browse/NIFI-6474 Project: Apache NiFi Issue Type: Task Components: FDS Reporter: Robert Fellows Migrating from @nifi-fds/core 0.1.0 to 0.2.0 also requires consuming apps to upgade to angular 8, rxjs 6, and others. This should be called out in the README and/or the Wiki so alert consumers of this lib of the impact upgrading might have on their application. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (NIFI-6455) Can't see config properties that overflow a scrollable list
[ https://issues.apache.org/jira/browse/NIFI-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16888312#comment-16888312 ] Robert Fellows commented on NIFI-6455: -- Pull Request submitted: https://github.com/apache/nifi/pull/3591 > Can't see config properties that overflow a scrollable list > --- > > Key: NIFI-6455 > URL: https://issues.apache.org/jira/browse/NIFI-6455 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.10.0 >Reporter: Peter Wicks >Assignee: Robert Fellows >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > When editing properties in a scrollable property configuration window, such > as in the Processor Configure window or the Controller Service Configure > window. > If the number of properties is too large to fit in the scroll window, than > one (or more?) of the properties will be inaccessible at the bottom. The > weird thing is the scrollbar is the right size, you just can't scroll down > that far. > I used GetSolr as my test case, as it has so many properties. > I tested in 1.9.2 and was not able to reproduce the issue, but in 1.10 it > shows up. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (NIFI-6455) Can't see config properties that overflow a scrollable list
[ https://issues.apache.org/jira/browse/NIFI-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16888303#comment-16888303 ] Robert Fellows commented on NIFI-6455: -- It appears to be related to the version of slickgrid used. Upgrading the version of that resolves the issue for me. Im putting together a commit for it now. > Can't see config properties that overflow a scrollable list > --- > > Key: NIFI-6455 > URL: https://issues.apache.org/jira/browse/NIFI-6455 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.10.0 >Reporter: Peter Wicks >Assignee: Robert Fellows >Priority: Major > > When editing properties in a scrollable property configuration window, such > as in the Processor Configure window or the Controller Service Configure > window. > If the number of properties is too large to fit in the scroll window, than > one (or more?) of the properties will be inaccessible at the bottom. The > weird thing is the scrollbar is the right size, you just can't scroll down > that far. > I used GetSolr as my test case, as it has so many properties. > I tested in 1.9.2 and was not able to reproduce the issue, but in 1.10 it > shows up. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6455) Can't see config properties that overflow a scrollable list
[ https://issues.apache.org/jira/browse/NIFI-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16888303#comment-16888303 ] Robert Fellows edited comment on NIFI-6455 at 7/18/19 8:21 PM: --- It appears to be related to the version of slickgrid used. Upgrading the version of that (to 2.3.23) resolves the issue for me. Im putting together a commit for it now. was (Author: rfellows): It appears to be related to the version of slickgrid used. Upgrading the version of that resolves the issue for me. Im putting together a commit for it now. > Can't see config properties that overflow a scrollable list > --- > > Key: NIFI-6455 > URL: https://issues.apache.org/jira/browse/NIFI-6455 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.10.0 >Reporter: Peter Wicks >Assignee: Robert Fellows >Priority: Major > > When editing properties in a scrollable property configuration window, such > as in the Processor Configure window or the Controller Service Configure > window. > If the number of properties is too large to fit in the scroll window, than > one (or more?) of the properties will be inaccessible at the bottom. The > weird thing is the scrollbar is the right size, you just can't scroll down > that far. > I used GetSolr as my test case, as it has so many properties. > I tested in 1.9.2 and was not able to reproduce the issue, but in 1.10 it > shows up. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (NIFI-6455) Can't see config properties that overflow a scrollable list
[ https://issues.apache.org/jira/browse/NIFI-6455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6455: Assignee: Robert Fellows > Can't see config properties that overflow a scrollable list > --- > > Key: NIFI-6455 > URL: https://issues.apache.org/jira/browse/NIFI-6455 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.10.0 >Reporter: Peter Wicks >Assignee: Robert Fellows >Priority: Major > > When editing properties in a scrollable property configuration window, such > as in the Processor Configure window or the Controller Service Configure > window. > If the number of properties is too large to fit in the scroll window, than > one (or more?) of the properties will be inaccessible at the bottom. The > weird thing is the scrollbar is the right size, you just can't scroll down > that far. > I used GetSolr as my test case, as it has so many properties. > I tested in 1.9.2 and was not able to reproduce the issue, but in 1.10 it > shows up. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (NIFI-6453) Support building nifi-fds on Windows
[ https://issues.apache.org/jira/browse/NIFI-6453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6453: Assignee: Robert Fellows > Support building nifi-fds on Windows > > > Key: NIFI-6453 > URL: https://issues.apache.org/jira/browse/NIFI-6453 > Project: Apache NiFi > Issue Type: Improvement > Components: FDS >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > > The current build architecture depends on bash scripts, preventing it from > being run on Windows systems (without cygwin). The goal would be to make it > os-agnostic. > One potential approach would be to leverage node.js for the pieces that > currently require a bash script. This includes things like: > * copying files (can use [rimraf|https://www.npmjs.com/package/rimraf]) > * creating directories (can use [mkdirp|https://www.npmjs.com/package/mkdirp]) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6453) Support building nifi-fds on Windows
Robert Fellows created NIFI-6453: Summary: Support building nifi-fds on Windows Key: NIFI-6453 URL: https://issues.apache.org/jira/browse/NIFI-6453 Project: Apache NiFi Issue Type: Improvement Components: FDS Reporter: Robert Fellows The current build architecture depends on bash scripts, preventing it from being run on Windows systems (without cygwin). The goal would be to make it os-agnostic. One potential approach would be to leverage node.js for the pieces that currently require a bash script. This includes things like: * copying files (can use [rimraf|https://www.npmjs.com/package/rimraf]) * creating directories (can use [mkdirp|https://www.npmjs.com/package/mkdirp]) -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (NIFI-6451) Unable to run clean:install
[ https://issues.apache.org/jira/browse/NIFI-6451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6451: Assignee: Robert Fellows > Unable to run clean:install > --- > > Key: NIFI-6451 > URL: https://issues.apache.org/jira/browse/NIFI-6451 > Project: Apache NiFi > Issue Type: Bug > Components: FDS >Reporter: Matt Gilman >Assignee: Robert Fellows >Priority: Major > Fix For: fds-0.2 > > > Running clean:install fails to run eslint unless install is ran from the root > directory first. It appears to be related to running npm to execute the > clean:install script and loading the eslint configuration from the root > directory prior to installation in the working directory in the target. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6450) Update Table component to use theme colors.
Robert Fellows created NIFI-6450: Summary: Update Table component to use theme colors. Key: NIFI-6450 URL: https://issues.apache.org/jira/browse/NIFI-6450 Project: Apache NiFi Issue Type: Improvement Components: FDS Reporter: Robert Fellows Assignee: Robert Fellows The row styling on hover should us theme-defined colors. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (NIFI-6446) Update button toggles to be themeable
[ https://issues.apache.org/jira/browse/NIFI-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6446: Assignee: Robert Fellows > Update button toggles to be themeable > - > > Key: NIFI-6446 > URL: https://issues.apache.org/jira/browse/NIFI-6446 > Project: Apache NiFi > Issue Type: Bug > Components: FDS >Reporter: Scott Aslan >Assignee: Robert Fellows >Priority: Major > Fix For: fds-0.2 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (NIFI-6445) Update Radio button to be themeable
[ https://issues.apache.org/jira/browse/NIFI-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6445: Assignee: Robert Fellows > Update Radio button to be themeable > --- > > Key: NIFI-6445 > URL: https://issues.apache.org/jira/browse/NIFI-6445 > Project: Apache NiFi > Issue Type: Bug > Components: FDS >Reporter: Scott Aslan >Assignee: Robert Fellows >Priority: Major > Fix For: fds-0.2 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6449) DemoApp - Add links and ids to each of the components to make navigation a bit easier
Robert Fellows created NIFI-6449: Summary: DemoApp - Add links and ids to each of the components to make navigation a bit easier Key: NIFI-6449 URL: https://issues.apache.org/jira/browse/NIFI-6449 Project: Apache NiFi Issue Type: Improvement Components: FDS Reporter: Robert Fellows Assignee: Robert Fellows It would be really nice to be able to navigate directly to the component desired in the demo app like: http://localhost:28080/#ExpansionPanels and have it take the user right to the Expansion Panels section so they don't have to scroll to find it.. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (NIFI-6444) Update expansion panel open arrow to be themeable
[ https://issues.apache.org/jira/browse/NIFI-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6444: Assignee: Robert Fellows > Update expansion panel open arrow to be themeable > - > > Key: NIFI-6444 > URL: https://issues.apache.org/jira/browse/NIFI-6444 > Project: Apache NiFi > Issue Type: Bug > Components: FDS >Reporter: Scott Aslan >Assignee: Robert Fellows >Priority: Major > Fix For: fds-0.2 > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6434) UI - Upgrade javascript dependencies in nifi-fds
Robert Fellows created NIFI-6434: Summary: UI - Upgrade javascript dependencies in nifi-fds Key: NIFI-6434 URL: https://issues.apache.org/jira/browse/NIFI-6434 Project: Apache NiFi Issue Type: Task Components: FDS Reporter: Robert Fellows Assignee: Robert Fellows There are some dependencies that are out of date. Update js dependencies (where they make sense). -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6397) UI - isolate webpack loaders used specifically for code coverage purposes
Robert Fellows created NIFI-6397: Summary: UI - isolate webpack loaders used specifically for code coverage purposes Key: NIFI-6397 URL: https://issues.apache.org/jira/browse/NIFI-6397 Project: Apache NiFi Issue Type: Task Components: FDS Reporter: Robert Fellows Assignee: Robert Fellows The jsDev and tsDev loaders are mis-named. They should be renamed to jsCoverage and tsCoverage. Also, these loaders should specify a different directory for their usage of the cache-loader to avoid conflicts with normal webpack configs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-289) UI - isolate webpack loaders used specifically for code coverage purposes
Robert Fellows created NIFIREG-289: -- Summary: UI - isolate webpack loaders used specifically for code coverage purposes Key: NIFIREG-289 URL: https://issues.apache.org/jira/browse/NIFIREG-289 Project: NiFi Registry Issue Type: Task Reporter: Robert Fellows Assignee: Robert Fellows The jsDev and tsDev loaders are mis-named. They should be renamed to jsCoverage and tsCoverage. Also, these loaders should specify a different directory for their usage of the cache-loader to avoid conflicts with normal webpack configs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6351) Allow for consistent angular template/templateUrl inclusion between JS and TS.
Robert Fellows created NIFI-6351:
Summary: Allow for consistent angular template/templateUrl
inclusion between JS and TS.
Key: NIFI-6351
URL: https://issues.apache.org/jira/browse/NIFI-6351
Project: Apache NiFi
Issue Type: Task
Components: FDS
Reporter: Robert Fellows
Assignee: Robert Fellows
In the JS files, we can
{noformat}
import template from './my-component.html'
{noformat}
and then reference that template in the component declaration.
However, if you try to do the same thing in a TS file, you get:
"Error: No template specified for component X"
at runtime. This can be solved by using:
{noformat}
const template = require('./my-component.html')
{noformat}
However, this would just be an inconsistency in how we define the components
purely based on the file type.
One solution is to standardize on templateUrl in the component declaration
{noformat}
templateUrl: './my-component.html'
{noformat}
And then chain a custom webpack loader for both file types that finds any
reference to {{tempateUrl: './component.html'}} and converts it at build time
to {{template: require('./component.html')}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFIREG-278) UI: Upgrade jQuery
[ https://issues.apache.org/jira/browse/NIFIREG-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFIREG-278: --- Issue Type: Task (was: Bug) > UI: Upgrade jQuery > -- > > Key: NIFIREG-278 > URL: https://issues.apache.org/jira/browse/NIFIREG-278 > Project: NiFi Registry > Issue Type: Task >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > > Upgrade jQuery to the latest version. > Upgrade any other important dependencies that might need it based on an npm > audit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-278) UI: Upgrade jQuery
Robert Fellows created NIFIREG-278: -- Summary: UI: Upgrade jQuery Key: NIFIREG-278 URL: https://issues.apache.org/jira/browse/NIFIREG-278 Project: NiFi Registry Issue Type: Bug Reporter: Robert Fellows Assignee: Robert Fellows Upgrade jQuery to the latest version. Upgrade any other important dependencies that might need it based on an npm audit. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFIREG-277) UI - Allow for consistent angular template/templateUrl inclusion between JS and TS.
[
https://issues.apache.org/jira/browse/NIFIREG-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Fellows reassigned NIFIREG-277:
--
Assignee: Robert Fellows
> UI - Allow for consistent angular template/templateUrl inclusion between JS
> and TS.
> ---
>
> Key: NIFIREG-277
> URL: https://issues.apache.org/jira/browse/NIFIREG-277
> Project: NiFi Registry
> Issue Type: Bug
>Reporter: Robert Fellows
>Assignee: Robert Fellows
>Priority: Major
>
> In the JS files, we can
> {noformat}
> import template from './my-component.html'
> {noformat}
> and then reference that template in the component declaration.
> However, if you try to do the same thing in a TS file, you get:
> "Error: No template specified for component X"
> at runtime. This can be solved by using:
> {noformat}
> const template = require('./my-component.html')
> {noformat}
> However, this would just be an inconsistency in how we define the components
> purely based on the file type.
> One solution is to standardize on templateUrl in the component declaration
> {noformat}
> templateUrl: './my-component.html'
> {noformat}
> And then chain a custom webpack loader for both file types that finds any
> reference to {{tempateUrl: './component.html'}} and converts it at build time
> to {{template: require('./component.html')}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (NIFIREG-277) UI - Allow for consistent angular template/templateUrl inclusion between JS and TS.
Robert Fellows created NIFIREG-277:
--
Summary: UI - Allow for consistent angular template/templateUrl
inclusion between JS and TS.
Key: NIFIREG-277
URL: https://issues.apache.org/jira/browse/NIFIREG-277
Project: NiFi Registry
Issue Type: Bug
Reporter: Robert Fellows
In the JS files, we can
{noformat}
import template from './my-component.html'
{noformat}
and then reference that template in the component declaration.
However, if you try to do the same thing in a TS file, you get:
"Error: No template specified for component X"
at runtime. This can be solved by using:
{noformat}
const template = require('./my-component.html')
{noformat}
However, this would just be an inconsistency in how we define the components
purely based on the file type.
One solution is to standardize on templateUrl in the component declaration
{noformat}
templateUrl: './my-component.html'
{noformat}
And then chain a custom webpack loader for both file types that finds any
reference to {{tempateUrl: './component.html'}} and converts it at build time
to {{template: require('./component.html')}}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFIREG-261) UI - introduce webpack, ES6, linting, dev build watch
[ https://issues.apache.org/jira/browse/NIFIREG-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows updated NIFIREG-261: --- Summary: UI - introduce webpack, ES6, linting, dev build watch (was: UI - introduce webpack, ES6, TS, linting, dev build watch) > UI - introduce webpack, ES6, linting, dev build watch > - > > Key: NIFIREG-261 > URL: https://issues.apache.org/jira/browse/NIFIREG-261 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > Time Spent: 2h 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (NIFI-6253) UI - Process Group ID display in "Operate" palette can get out of sync when process groups are removed from different sessions.
[ https://issues.apache.org/jira/browse/NIFI-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reopened NIFI-6253: -- The original fix has a regression. Re-opening to fix it. The issue manifests in an error/warning dialog to the user when they add/edit/delete a policy. This happens on a call to the nfCanvasUtils.reload method. That method no longer expects an object parameter that it is invocation sends it. It only accepts an optional numeric value for the process group id to reload. > UI - Process Group ID display in "Operate" palette can get out of sync when > process groups are removed from different sessions. > --- > > Key: NIFI-6253 > URL: https://issues.apache.org/jira/browse/NIFI-6253 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.9.2 >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > Fix For: 1.10.0 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > To reproduce this issue: > # Open Nifi in 2 different browser tabs > # Add two process groups to the canvas in one tab, then refresh the other tab > to get the updates. > # Take note of the Process Group IDs displayed in the "Operate" palette when > selecting each one in the canvas. > # Take note of the Process Group ID for the entire Flow displayed in the > "Operate" palette (clicking on a blank spot on the canvas will update the > palette) > # In one of the browser tabs, delete one of the process groups. > # Quickly switch to the other browser tab and double click on the process > group you deleted in the other tab to attempt to enter that process group. > # You should see a dialog indicating something to the effect of this process > group is not able to be located (this is expected) > # Now click on a blank spot on the canvas. Notice that the process group id > displayed for the Flow is id for the process group that was deleted and NOT > for the flow. > # Expected: Clicking on the canvas should update the process group id in the > "Operate" palette to the proper id following the failure to enter a process > group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFI-6316) UI - Upgrade jQuery
[ https://issues.apache.org/jira/browse/NIFI-6316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6316: Assignee: Robert Fellows > UI - Upgrade jQuery > --- > > Key: NIFI-6316 > URL: https://issues.apache.org/jira/browse/NIFI-6316 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Reporter: Matt Gilman >Assignee: Robert Fellows >Priority: Major > > Upgrade to a newer version of jQuery. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFIREG-98) Add favicon to Registry documentation
[ https://issues.apache.org/jira/browse/NIFIREG-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFIREG-98: - Assignee: Robert Fellows > Add favicon to Registry documentation > - > > Key: NIFIREG-98 > URL: https://issues.apache.org/jira/browse/NIFIREG-98 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.1.0 >Reporter: Andrew Lim >Assignee: Robert Fellows >Priority: Trivial > > The Registry application has a favicon. Same one should be there for the > documentation. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6253) UI - Process Group ID display in "Operate" palette can get out of sync when process groups are removed from different sessions.
Robert Fellows created NIFI-6253: Summary: UI - Process Group ID display in "Operate" palette can get out of sync when process groups are removed from different sessions. Key: NIFI-6253 URL: https://issues.apache.org/jira/browse/NIFI-6253 Project: Apache NiFi Issue Type: Bug Components: Core UI Affects Versions: 1.9.2 Reporter: Robert Fellows Assignee: Robert Fellows To reproduce this issue: # Open Nifi in 2 different browser tabs # Add two process groups to the canvas in one tab, then refresh the other tab to get the updates. # Take note of the Process Group IDs displayed in the "Operate" palette when selecting each one in the canvas. # Take note of the Process Group ID for the entire Flow displayed in the "Operate" palette (clicking on a blank spot on the canvas will update the palette) # In one of the browser tabs, delete one of the process groups. # Quickly switch to the other browser tab and double click on the process group you deleted in the other tab to attempt to enter that process group. # You should see a dialog indicating something to the effect of this process group is not able to be located (this is expected) # Now click on a blank spot on the canvas. Notice that the process group id displayed for the Flow is id for the process group that was deleted and NOT for the flow. # Expected: Clicking on the canvas should update the process group id in the "Operate" palette to the proper id following the failure to enter a process group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFIREG-261) UI - introduce webpack, ES6, TS, linting, dev build watch
[ https://issues.apache.org/jira/browse/NIFIREG-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFIREG-261: -- Assignee: Robert Fellows > UI - introduce webpack, ES6, TS, linting, dev build watch > - > > Key: NIFIREG-261 > URL: https://issues.apache.org/jira/browse/NIFIREG-261 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-261) UI - introduce webpack, ES6, TS, linting, dev build watch
Robert Fellows created NIFIREG-261: -- Summary: UI - introduce webpack, ES6, TS, linting, dev build watch Key: NIFIREG-261 URL: https://issues.apache.org/jira/browse/NIFIREG-261 Project: NiFi Registry Issue Type: Improvement Reporter: Robert Fellows -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6249) UI - Provide nifi-fds es6 modules that require no aliasing of nifi-fds directory structure.
Robert Fellows created NIFI-6249:
Summary: UI - Provide nifi-fds es6 modules that require no
aliasing of nifi-fds directory structure.
Key: NIFI-6249
URL: https://issues.apache.org/jira/browse/NIFI-6249
Project: Apache NiFi
Issue Type: Improvement
Components: FDS
Reporter: Robert Fellows
Assignee: Robert Fellows
nifi-fds uses aliases in some/many import/require statements that force
consumers of the package to also alias them. This adds a complexity to the
configuration that could be mitigated for ES6 consumers. The ideal solution
would allow consuming apps to install @nifi-fds/core and then import it's
modules without needing to know anything internally to how nifi-fds is
structured.
Examples might look something like this...
{noformat}
import { FdsCoreModule } from '@nifi-fds/core'
// or
import { FdsDialogService, FdsSnackBarService, FdsCoasterComponent } from
'@nifi-fds/core'
{noformat}
Also, update the README to reflect updates.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (NIFI-6247) UI - text input components should default to a white background and use the theme accent color as the border-color when focused
Robert Fellows created NIFI-6247: Summary: UI - text input components should default to a white background and use the theme accent color as the border-color when focused Key: NIFI-6247 URL: https://issues.apache.org/jira/browse/NIFI-6247 Project: Apache NiFi Issue Type: Bug Components: FDS Reporter: Robert Fellows Assignee: Robert Fellows UI - text input components should default to a white background and use the theme accent color as the border-color when focused -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6237) UI - Text in filter (td-chips) input can overlap the filter icon.
Robert Fellows created NIFI-6237: Summary: UI - Text in filter (td-chips) input can overlap the filter icon. Key: NIFI-6237 URL: https://issues.apache.org/jira/browse/NIFI-6237 Project: Apache NiFi Issue Type: Bug Components: FDS Reporter: Robert Fellows Assignee: Robert Fellows When using the component, text will overlap the filter icon on the right side of the input when it gets long enough. Also, the underline beneath the input is shorter than the input itself. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (NIFI-6126) Change nf-canvas to respond to keyup events rather than keydown
[ https://issues.apache.org/jira/browse/NIFI-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reopened NIFI-6126: -- We can't depend on keyup events for our hotkeys. If we wait for keyup, the browser's own key listeners can act on the events first and change the event details that indicate the metaKey was active at the time of the event. That information gets removed. As a result, CMD-R, CMD-A and the like are not functional as they used to be when we attached to keydown. So, the solution should be to once again attach to keydown but throttle the requests to canvas reload to only allow a request once every so many milliseconds to prevent potential overloading of the server with requests when holding down CTRL-R (or CMD-R). That was the real impetus for this case originally. > Change nf-canvas to respond to keyup events rather than keydown > --- > > Key: NIFI-6126 > URL: https://issues.apache.org/jira/browse/NIFI-6126 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.9.0 >Reporter: Robert Fellows >Assignee: Robert Fellows >Priority: Major > Fix For: 1.10.0 > > Time Spent: 40m > Remaining Estimate: 0h > > nf-canvas responds to keydown events currently. This allows for a scenario > where the user can hold down CTRL + R and continuously refresh the canvas, > sending many requests to the server and potentially cause a Denial of Service. > It really should be listening for keyup instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFI-6136) UI - User and Template bug when page popped out
[ https://issues.apache.org/jira/browse/NIFI-6136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-6136: Assignee: Robert Fellows > UI - User and Template bug when page popped out > --- > > Key: NIFI-6136 > URL: https://issues.apache.org/jira/browse/NIFI-6136 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Reporter: Matt Gilman >Assignee: Robert Fellows >Priority: Minor > > When running in standalone mode, if the user pops out the users page or the > templates page a warning about running in disconnected mode is presented. > This warning is shown without considering whether the current NiFi instance > is even configured for clustering. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6140) Incorrect title on the read only version of the Reporting Task detail dialog
Robert Fellows created NIFI-6140: Summary: Incorrect title on the read only version of the Reporting Task detail dialog Key: NIFI-6140 URL: https://issues.apache.org/jira/browse/NIFI-6140 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Robert Fellows Assignee: Robert Fellows The read-only version of the Reporting Task dialog has the title "Configure Reporting Task", leading the user to assume that it is editable. It should read "Reporting Task Details". -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFI-4230) Use a better default location when pasting via keystokes outside the context of the originally selected components
[ https://issues.apache.org/jira/browse/NIFI-4230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Fellows reassigned NIFI-4230: Assignee: Robert Fellows (was: Matt Gilman) > Use a better default location when pasting via keystokes outside the context > of the originally selected components > -- > > Key: NIFI-4230 > URL: https://issues.apache.org/jira/browse/NIFI-4230 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.3.0 >Reporter: Daniel Chaffelson >Assignee: Robert Fellows >Priority: Minor > > When copy/pasting components between different Process Groups, the keystroke > behavior differs from the right-click behavior. Specifically, it does not > paste the components on the current focus area of the canvas, but appears to > paste them relative to their original position in the original context, which > effectively puts them somewhere random on the focus canvas, requiring the > user to hunt them down. > It would be optimal to select a better default location somewhere in the > focus area of the canvas for all paste behaviors consistently. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6126) Change nf-canvas to respond to keyup events rather than keydown
Robert Fellows created NIFI-6126: Summary: Change nf-canvas to respond to keyup events rather than keydown Key: NIFI-6126 URL: https://issues.apache.org/jira/browse/NIFI-6126 Project: Apache NiFi Issue Type: Bug Components: Core UI Affects Versions: 1.9.0 Reporter: Robert Fellows Assignee: Robert Fellows nf-canvas responds to keydown events currently. This allows for a scenario where the user can hold down CTRL + R and continuously refresh the canvas, sending many requests to the server and potentially cause a Denial of Service. It really should be listening for keyup instead. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6118) UI - Not all calls to nfCanvasUtil.reloadConnectionSourceAndDestination are made with the proper component IDs
Robert Fellows created NIFI-6118:
Summary: UI - Not all calls to
nfCanvasUtil.reloadConnectionSourceAndDestination are made with the proper
component IDs
Key: NIFI-6118
URL: https://issues.apache.org/jira/browse/NIFI-6118
Project: Apache NiFi
Issue Type: Bug
Components: Core UI
Reporter: Robert Fellows
Assignee: Robert Fellows
There are a handful of calls to
{code}nfCanvasUtil.reloadConnectionSourceAndDestination{code} that are made
with component IDs that are taken directly off of the connection object rather
than using the utility functions getConnectionSourceComponentId or
getConnectionDestinationComponentId that are group-aware and return the proper
IDs accordingly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
