[jira] [Commented] (NIFI-6685) Sort and aling
[ https://issues.apache.org/jira/browse/NIFI-6685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16937046#comment-16937046 ] Andrew Lim commented on NIFI-6685: -- [~Nitin108], there is no component sort feature but are you aware of the component alignment functionality ([https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#component_alignment)] ? > Sort and aling > -- > > Key: NIFI-6685 > URL: https://issues.apache.org/jira/browse/NIFI-6685 > Project: Apache NiFi > Issue Type: Wish > Components: Core UI >Reporter: Nitin Ullal >Priority: Major > Attachments: nifi.png > > > It would be nice to have a feature that sorts and aligns Process Groups by > their name and aligns them to a grid (for example 3x3). > Check out attached screenshot. Every time I add something I have to manually > sort and align. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (NIFI-6700) Link to contributor guide in online documentation broken
[ https://issues.apache.org/jira/browse/NIFI-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16936896#comment-16936896 ] Andrew Lim commented on NIFI-6700: -- I can reproduce the issue. The URL of the link is correct. The problem is the page tries to render within the Developer Guide and fails. Will make the link open in a different browser tab. > Link to contributor guide in online documentation broken > > > Key: NIFI-6700 > URL: https://issues.apache.org/jira/browse/NIFI-6700 > Project: Apache NiFi > Issue Type: Task >Reporter: Otto Fowler >Assignee: Andrew Lim >Priority: Major > > The link to the contributing guide in the developer's guide off of > https://nifi.apache.org/docs/nifi-docs/ doesn't work -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (NIFI-6700) Link to contributor guide in online documentation broken
[ https://issues.apache.org/jira/browse/NIFI-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-6700: Assignee: Andrew Lim > Link to contributor guide in online documentation broken > > > Key: NIFI-6700 > URL: https://issues.apache.org/jira/browse/NIFI-6700 > Project: Apache NiFi > Issue Type: Task >Reporter: Otto Fowler >Assignee: Andrew Lim >Priority: Major > > The link to the contributing guide in the developer's guide off of > https://nifi.apache.org/docs/nifi-docs/ doesn't work -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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:comment-tabpanel=16936116#comment-16936116 ] Andrew Lim commented on NIFI-6671: -- Verified fix. > 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 > Fix For: 1.10.0 > > Attachments: alphabetical_order.png, wrong-order.png > > Time Spent: 40m > 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.4#803005)
[jira] [Commented] (NIFI-6558) Add documentation for Parameters
[ https://issues.apache.org/jira/browse/NIFI-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932556#comment-16932556 ] Andrew Lim commented on NIFI-6558: -- Also need to update the "Managing Local Changes" section with content related to parameters. > Add documentation for Parameters > > > Key: NIFI-6558 > URL: https://issues.apache.org/jira/browse/NIFI-6558 > Project: Apache NiFi > Issue Type: Sub-task > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > Fix For: 1.10.0 > > Time Spent: 5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (NIFI-6558) Add documentation for Parameters
[ https://issues.apache.org/jira/browse/NIFI-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reopened NIFI-6558: -- The "Parameters and Versioned Flows" section can be made clearer. Will add an example/screenshots to make it more readable/understandable. > Add documentation for Parameters > > > Key: NIFI-6558 > URL: https://issues.apache.org/jira/browse/NIFI-6558 > Project: Apache NiFi > Issue Type: Sub-task > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > Fix For: 1.10.0 > > Time Spent: 5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.2#803003)
[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 ] Andrew Lim updated NIFI-6671: - Attachment: alphabetical_order.png > 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 >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-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 ] Andrew Lim updated NIFI-6671: - Attachment: wrong-order.png > 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 >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] [Created] (NIFI-6671) UI:Parameters listed in "Reference parameter..." drop-down not listed alphabetically
Andrew Lim created NIFI-6671: Summary: 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 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] [Commented] (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:comment-tabpanel=16927622#comment-16927622
]
Andrew Lim commented on NIFI-6634:
--
[~rfellows] The URL of the section I am adding to the User Guide is:
{{nifi-docs/html/user-guide.html#Parameters}}
> 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] [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 ] Andrew Lim updated NIFI-6641: - Component/s: Core UI > 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 > > 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] [Commented] (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:comment-tabpanel=16924446#comment-16924446 ] Andrew Lim commented on NIFI-6634: -- Thanks [~rmoran], makes sense! For reference, the Parameters section is being added to the User Guide via NIFI-6558. > 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 >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] [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 ] Andrew Lim updated NIFI-6641: - Description: 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. was: 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. > 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 >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-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 ] Andrew Lim updated NIFI-6641: - Parent: NIFI-6276 Issue Type: Sub-task (was: Bug) > 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 >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] [Created] (NIFI-6641) UI:Parameter Context dialog needs to support non-editable scenario
Andrew Lim created NIFI-6641: Summary: 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: Bug Reporter: Andrew Lim 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] [Comment Edited] (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:comment-tabpanel=16924369#comment-16924369 ] Andrew Lim edited comment on NIFI-6634 at 9/6/19 4:15 PM: -- Here's a draft of what I was going to add to the User Guide as a Warning in the Variables section: Variables are still supported for compatibility purposes but do not have the same power as Parameters such as support for sensitive properties and more granular control over who can create, modify or use them. Variables will be removed in a future release. As a result, it is highly recommended to switch to Parameters. If that is too verbose to add to the Variables dialog, perhaps this: Variables are still supported for compatibility purposes but do not have the same power as Parameters such as support for sensitive properties. Please switch to Parameters as Variables will be removed in a future release. was (Author: andrewmlim): Here's a draft of what I was going to add to the User Guide as a Note in the Variables section: Variables are still supported for compatibility purposes but do not have the same power as Parameters such as support for sensitive properties and more granular control over who can create, modify or use them. Variables will be removed in a future release. As a result, it is highly recommended to switch to Parameters. If that is too verbose to add to the Variables dialog, perhaps this: Variables are still supported for compatibility purposes but do not have the same power as Parameters such as support for sensitive properties. Please switch to Parameters as Variables will be removed in a future release. > 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 >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] [Commented] (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:comment-tabpanel=16924369#comment-16924369 ] Andrew Lim commented on NIFI-6634: -- Here's a draft of what I was going to add to the User Guide as a Note in the Variables section: Variables are still supported for compatibility purposes but do not have the same power as Parameters such as support for sensitive properties and more granular control over who can create, modify or use them. Variables will be removed in a future release. As a result, it is highly recommended to switch to Parameters. If that is too verbose to add to the Variables dialog, perhaps this: Variables are still supported for compatibility purposes but do not have the same power as Parameters such as support for sensitive properties. Please switch to Parameters as Variables will be removed in a future release. > 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 >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] [Commented] (NIFIREG-293) Highlight in Getting Started guide that only process groups can be versioned.
[ https://issues.apache.org/jira/browse/NIFIREG-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16922829#comment-16922829 ] Andrew Lim commented on NIFIREG-293: Made it more obvious by bolding that flows are versioned on the *process group level*. > Highlight in Getting Started guide that only process groups can be versioned. > - > > Key: NIFIREG-293 > URL: https://issues.apache.org/jira/browse/NIFIREG-293 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Trivial > > Received some feedback from new users that it wasn't clear in NiFi docs that > only Process Groups can be versioned. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFIREG-293) Highlight in Getting Started guide that only process groups can be versioned.
[ https://issues.apache.org/jira/browse/NIFIREG-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFIREG-293: --- Description: Received some feedback from new users that it wasn't clear in NiFi docs that only Process Groups can be versioned. (was: Received some feedback from new users of NiFi that only Process Groups can be versioned.) > Highlight in Getting Started guide that only process groups can be versioned. > - > > Key: NIFIREG-293 > URL: https://issues.apache.org/jira/browse/NIFIREG-293 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Trivial > > Received some feedback from new users that it wasn't clear in NiFi docs that > only Process Groups can be versioned. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Resolved] (NIFIREG-284) Update docs for newly added granular proxy policies
[ https://issues.apache.org/jira/browse/NIFIREG-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim resolved NIFIREG-284. Fix Version/s: 0.6.0 Resolution: Fixed Fix included in NIFIREG-316. > Update docs for newly added granular proxy policies > --- > > Key: NIFIREG-284 > URL: https://issues.apache.org/jira/browse/NIFIREG-284 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > Labels: migration > Fix For: 0.6.0 > > > Read/write/delete policies added via NIFIREG-212 > At minimum, need to update screenshots as a result. But can also add more > information for possible use cases with these policies. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (NIFI-6608) UI: Reporting Task Controller Services should not show that Parameters are supported
[ https://issues.apache.org/jira/browse/NIFI-6608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-6608: - Attachment: reporting_task_cs_property.png > UI: Reporting Task Controller Services should not show that Parameters are > supported > > > Key: NIFI-6608 > URL: https://issues.apache.org/jira/browse/NIFI-6608 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Andrew Lim >Priority: Major > Attachments: reporting_task_cs_property.png > > > As shown in the attached screenshot, the UI shows that Parameters are > supported for Reporting Task Controller Services properties even though this > is not true. > The behavior is correct for Reporting Tasks. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6608) UI: Reporting Task Controller Services should not show that Parameters are supported
Andrew Lim created NIFI-6608: Summary: UI: Reporting Task Controller Services should not show that Parameters are supported Key: NIFI-6608 URL: https://issues.apache.org/jira/browse/NIFI-6608 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Andrew Lim As shown in the attached screenshot, the UI shows that Parameters are supported for Reporting Task Controller Services properties even though this is not true. The behavior is correct for Reporting Tasks. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6607) UI: State of referencing processors in Parameter Context dialog do not update after "Apply"
Andrew Lim created NIFI-6607: Summary: 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 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] [Created] (NIFI-6603) Variables: There is no way to cancel creating a new variable unless a variable name is provided.
Andrew Lim created NIFI-6603: Summary: Variables: There is no way to cancel creating a new variable unless a variable name is provided. Key: NIFI-6603 URL: https://issues.apache.org/jira/browse/NIFI-6603 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: Andrew Lim Open the variables window and select "+" . In the New Variable window do not enter a value for the Variable Name field and select "OK". A Configuration Error dialog is shown, select "OK". There is no way for the user to stop variable creation without entering a name and then selecting Cancel from the Variables window. We should add a "Cancel" button to the "New Variable" window. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFI-6602) Parameters: "Apply" button should be greyed out if no changes have been
Andrew Lim created NIFI-6602: Summary: 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: Improvement Components: Core UI Reporter: Andrew Lim 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] [Created] (NIFI-6601) Variables: "Apply" button should be greyed out if no changes have been made
Andrew Lim created NIFI-6601: Summary: Variables: "Apply" button should be greyed out if no changes have been made Key: NIFI-6601 URL: https://issues.apache.org/jira/browse/NIFI-6601 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: Andrew Lim After opening the Variables window, 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. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFIREG-314) Remove references to HipChat from README
[ https://issues.apache.org/jira/browse/NIFIREG-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFIREG-314: -- Assignee: Andrew Lim > Remove references to HipChat from README > > > Key: NIFIREG-314 > URL: https://issues.apache.org/jira/browse/NIFIREG-314 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Denes Arvay >Assignee: Andrew Lim >Priority: Trivial > > and update it similarly as it was done in NiFi (NIFI-6460) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (NIFIREG-314) Remove references to HipChat from README
[ https://issues.apache.org/jira/browse/NIFIREG-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16916029#comment-16916029 ] Andrew Lim commented on NIFIREG-314: Thanks for filing this [~denes]. Did you see any other references to HipChat besides in nifi-registry/nifi-registry-assembly/README.md ? Just wanted to make sure that was the only one. > Remove references to HipChat from README > > > Key: NIFIREG-314 > URL: https://issues.apache.org/jira/browse/NIFIREG-314 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Denes Arvay >Assignee: Andrew Lim >Priority: Trivial > > and update it similarly as it was done in NiFi (NIFI-6460) -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (NIFIREG-284) Update docs for newly added granular proxy policies
[ https://issues.apache.org/jira/browse/NIFIREG-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914579#comment-16914579 ] Andrew Lim commented on NIFIREG-284: Incorporated these changes into PR for NIFIREG-316. Will close this out once that ticket has been resolved. > Update docs for newly added granular proxy policies > --- > > Key: NIFIREG-284 > URL: https://issues.apache.org/jira/browse/NIFIREG-284 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > Labels: migration > > Read/write/delete policies added via NIFIREG-212 > At minimum, need to update screenshots as a result. But can also add more > information for possible use cases with these policies. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (NIFIREG-316) Add/update documentation for public buckets
[ https://issues.apache.org/jira/browse/NIFIREG-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914539#comment-16914539 ] Andrew Lim commented on NIFIREG-316: Noticed that there wasn't any doc added for the "Allow bundle overwrite" setting when editing a bucket. Will add these updates as well. > Add/update documentation for public buckets > --- > > Key: NIFIREG-316 > URL: https://issues.apache.org/jira/browse/NIFIREG-316 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > > Need to add/update documentation for the new feature of public buckets. > The option "Make publicly available" is now available when creating buckets. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (NIFIREG-284) Update docs for newly added granular proxy policies
[ https://issues.apache.org/jira/browse/NIFIREG-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914385#comment-16914385 ] Andrew Lim commented on NIFIREG-284: Administration Guide was updated in the NIFIREG-212 PR, specifically in the "Special Privilege Policies" section. > Update docs for newly added granular proxy policies > --- > > Key: NIFIREG-284 > URL: https://issues.apache.org/jira/browse/NIFIREG-284 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > Labels: migration > > Read/write/delete policies added via NIFIREG-212 > At minimum, need to update screenshots as a result. But can also add more > information for possible use cases with these policies. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Commented] (NIFIREG-284) Update docs for newly added granular proxy policies
[ https://issues.apache.org/jira/browse/NIFIREG-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16914383#comment-16914383 ] Andrew Lim commented on NIFIREG-284: Migration Guide notes for 0.5.0 have been updated with the following text: The Proxy permissions were made more granular and now support specific permissions for Read, Write, and Delete. Any existing users that were granted the Proxy permission will end up with only Write permissions and will need to be granted Read and Delete. This primarily impacts the users that represent NiFi instances which will need Read and Write permissions to Proxy, in order to perform operations on behalf of the end users in NiFi. > Update docs for newly added granular proxy policies > --- > > Key: NIFIREG-284 > URL: https://issues.apache.org/jira/browse/NIFIREG-284 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > Labels: migration > > Read/write/delete policies added via NIFIREG-212 > At minimum, need to update screenshots as a result. But can also add more > information for possible use cases with these policies. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFIREG-316) Add/update documentation for public buckets
[ https://issues.apache.org/jira/browse/NIFIREG-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFIREG-316: -- Assignee: Andrew Lim > Add/update documentation for public buckets > --- > > Key: NIFIREG-316 > URL: https://issues.apache.org/jira/browse/NIFIREG-316 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > > Need to add/update documentation for the new feature of public buckets. > The option "Make publicly available" is now available when creating buckets. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (NIFIREG-316) Add/update documentation for public buckets
Andrew Lim created NIFIREG-316: -- Summary: Add/update documentation for public buckets Key: NIFIREG-316 URL: https://issues.apache.org/jira/browse/NIFIREG-316 Project: NiFi Registry Issue Type: Improvement Affects Versions: 0.5.0 Reporter: Andrew Lim Need to add/update documentation for the new feature of public buckets. The option "Make publicly available" is now available when creating buckets. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Assigned] (NIFI-6558) Add documentation for Parameters
[ https://issues.apache.org/jira/browse/NIFI-6558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-6558: Assignee: Andrew Lim > Add documentation for Parameters > > > Key: NIFI-6558 > URL: https://issues.apache.org/jira/browse/NIFI-6558 > Project: Apache NiFi > Issue Type: Sub-task > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6558) Add documentation for Parameters
Andrew Lim created NIFI-6558: Summary: Add documentation for Parameters Key: NIFI-6558 URL: https://issues.apache.org/jira/browse/NIFI-6558 Project: Apache NiFi Issue Type: Sub-task Components: Documentation Website Reporter: Andrew Lim -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (NIFI-5749) NiFi requirements include "Java 8 or later", but doesn't compile with Java 9
[ https://issues.apache.org/jira/browse/NIFI-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim resolved NIFI-5749. -- Resolution: Duplicate Closing this ticket because NIFI-6187 will handle all Java 11 related doc edits. > NiFi requirements include "Java 8 or later", but doesn't compile with Java 9 > > > Key: NIFI-5749 > URL: https://issues.apache.org/jira/browse/NIFI-5749 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation Website, Tools and Build >Affects Versions: 1.8.0 > Environment: Ubuntu 18.04.1 LTS, AMD64 >Reporter: Arpad Boda >Assignee: Andrew Lim >Priority: Major > > README.md file attached to NiFi release 1.8.0 contains the following: > _#__# Requirements_ > _JDK 1.8 or newer_ > However NiFi doesn't compile with Java 9: > _[ERROR] Failed to execute goal > org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc (output-html) > on project nifi-docs: Execution output-html of goal > org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc failed: > (LoadError) load error: jruby/java/java_ext/java.lang -- > java.lang.reflect.InaccessibleObjectException: Cannot make a non-public > member of class java.lang.reflect.AccessibleObject accessible -> [Help 1]_ > Either the content of readme or the compilation error should be fixed. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (NIFI-5749) NiFi requirements include "Java 8 or later", but doesn't compile with Java 9
[ https://issues.apache.org/jira/browse/NIFI-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16894050#comment-16894050 ] Andrew Lim commented on NIFI-5749: -- In nifi-assembly/README.md it says: JDK 1.8 or higher Will change to: Java 8 (ongoing work to enable NiFi to run on Java 11; see NIFI-5174) > NiFi requirements include "Java 8 or later", but doesn't compile with Java 9 > > > Key: NIFI-5749 > URL: https://issues.apache.org/jira/browse/NIFI-5749 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation Website, Tools and Build >Affects Versions: 1.8.0 > Environment: Ubuntu 18.04.1 LTS, AMD64 >Reporter: Arpad Boda >Assignee: Andrew Lim >Priority: Major > > README.md file attached to NiFi release 1.8.0 contains the following: > _#__# Requirements_ > _JDK 1.8 or newer_ > However NiFi doesn't compile with Java 9: > _[ERROR] Failed to execute goal > org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc (output-html) > on project nifi-docs: Execution output-html of goal > org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc failed: > (LoadError) load error: jruby/java/java_ext/java.lang -- > java.lang.reflect.InaccessibleObjectException: Cannot make a non-public > member of class java.lang.reflect.AccessibleObject accessible -> [Help 1]_ > Either the content of readme or the compilation error should be fixed. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (NIFI-5749) NiFi requirements include "Java 8 or later", but doesn't compile with Java 9
[ https://issues.apache.org/jira/browse/NIFI-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16894029#comment-16894029 ] Andrew Lim commented on NIFI-5749: -- In [https://github.com/apache/nifi/blob/master/README.md] it says: JDK 1.8 (_ongoing work to enable NiFi to run on Java 9/10/11; see NIFI-5174_) Will change to: Java 8 (ongoing work to enable NiFi to run on Java 11; see NIFI-5174) > NiFi requirements include "Java 8 or later", but doesn't compile with Java 9 > > > Key: NIFI-5749 > URL: https://issues.apache.org/jira/browse/NIFI-5749 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation Website, Tools and Build >Affects Versions: 1.8.0 > Environment: Ubuntu 18.04.1 LTS, AMD64 >Reporter: Arpad Boda >Assignee: Andrew Lim >Priority: Major > > README.md file attached to NiFi release 1.8.0 contains the following: > _#__# Requirements_ > _JDK 1.8 or newer_ > However NiFi doesn't compile with Java 9: > _[ERROR] Failed to execute goal > org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc (output-html) > on project nifi-docs: Execution output-html of goal > org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc failed: > (LoadError) load error: jruby/java/java_ext/java.lang -- > java.lang.reflect.InaccessibleObjectException: Cannot make a non-public > member of class java.lang.reflect.AccessibleObject accessible -> [Help 1]_ > Either the content of readme or the compilation error should be fixed. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (NIFI-5749) NiFi requirements include "Java 8 or later", but doesn't compile with Java 9
[ https://issues.apache.org/jira/browse/NIFI-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893860#comment-16893860 ] Andrew Lim commented on NIFI-5749: -- In the short term, will change from "Java 8 or later" to "Java 8". Will need to revisit once Java 11 work is complete (https://issues.apache.org/jira/browse/NIFI-5176). Filed https://issues.apache.org/jira/browse/NIFI-6491 to improve installation documentation in the longer term. > NiFi requirements include "Java 8 or later", but doesn't compile with Java 9 > > > Key: NIFI-5749 > URL: https://issues.apache.org/jira/browse/NIFI-5749 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation Website, Tools and Build >Affects Versions: 1.8.0 > Environment: Ubuntu 18.04.1 LTS, AMD64 >Reporter: Arpad Boda >Assignee: Andrew Lim >Priority: Major > > README.md file attached to NiFi release 1.8.0 contains the following: > _#__# Requirements_ > _JDK 1.8 or newer_ > However NiFi doesn't compile with Java 9: > _[ERROR] Failed to execute goal > org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc (output-html) > on project nifi-docs: Execution output-html of goal > org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc failed: > (LoadError) load error: jruby/java/java_ext/java.lang -- > java.lang.reflect.InaccessibleObjectException: Cannot make a non-public > member of class java.lang.reflect.AccessibleObject accessible -> [Help 1]_ > Either the content of readme or the compilation error should be fixed. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (NIFI-6491) Improve installation documentation
[ https://issues.apache.org/jira/browse/NIFI-6491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-6491: Assignee: Andrew Lim > Improve installation documentation > -- > > Key: NIFI-6491 > URL: https://issues.apache.org/jira/browse/NIFI-6491 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > > Provide more detailed instruction on using Homebrew to install NiFi as well > as how to install other necessary components (ie. the proper Java version). > Related NiFi Users mailing list thread: > https://lists.apache.org/thread.html/59719f821b560eff1bdaca87070184aea76af34a121f33607684601b@%3Cusers.nifi.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6491) Improve installation documentation
Andrew Lim created NIFI-6491: Summary: Improve installation documentation Key: NIFI-6491 URL: https://issues.apache.org/jira/browse/NIFI-6491 Project: Apache NiFi Issue Type: Improvement Components: Documentation Website Reporter: Andrew Lim Provide more detailed instruction on using Homebrew to install NiFi as well as how to install other necessary components (ie. the proper Java version). Related NiFi Users mailing list thread: https://lists.apache.org/thread.html/59719f821b560eff1bdaca87070184aea76af34a121f33607684601b@%3Cusers.nifi.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (NIFI-5749) NiFi requirements include "Java 8 or later", but doesn't compile with Java 9
[ https://issues.apache.org/jira/browse/NIFI-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-5749: Assignee: Andrew Lim > NiFi requirements include "Java 8 or later", but doesn't compile with Java 9 > > > Key: NIFI-5749 > URL: https://issues.apache.org/jira/browse/NIFI-5749 > Project: Apache NiFi > Issue Type: Bug > Components: Tools and Build >Affects Versions: 1.8.0 > Environment: Ubuntu 18.04.1 LTS, AMD64 >Reporter: Arpad Boda >Assignee: Andrew Lim >Priority: Major > > README.md file attached to NiFi release 1.8.0 contains the following: > _#__# Requirements_ > _JDK 1.8 or newer_ > However NiFi doesn't compile with Java 9: > _[ERROR] Failed to execute goal > org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc (output-html) > on project nifi-docs: Execution output-html of goal > org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc failed: > (LoadError) load error: jruby/java/java_ext/java.lang -- > java.lang.reflect.InaccessibleObjectException: Cannot make a non-public > member of class java.lang.reflect.AccessibleObject accessible -> [Help 1]_ > Either the content of readme or the compilation error should be fixed. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-5749) NiFi requirements include "Java 8 or later", but doesn't compile with Java 9
[ https://issues.apache.org/jira/browse/NIFI-5749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-5749: - Component/s: Documentation & Website > NiFi requirements include "Java 8 or later", but doesn't compile with Java 9 > > > Key: NIFI-5749 > URL: https://issues.apache.org/jira/browse/NIFI-5749 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation Website, Tools and Build >Affects Versions: 1.8.0 > Environment: Ubuntu 18.04.1 LTS, AMD64 >Reporter: Arpad Boda >Assignee: Andrew Lim >Priority: Major > > README.md file attached to NiFi release 1.8.0 contains the following: > _#__# Requirements_ > _JDK 1.8 or newer_ > However NiFi doesn't compile with Java 9: > _[ERROR] Failed to execute goal > org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc (output-html) > on project nifi-docs: Execution output-html of goal > org.asciidoctor:asciidoctor-maven-plugin:1.5.2:process-asciidoc failed: > (LoadError) load error: jruby/java/java_ext/java.lang -- > java.lang.reflect.InaccessibleObjectException: Cannot make a non-public > member of class java.lang.reflect.AccessibleObject accessible -> [Help 1]_ > Either the content of readme or the compilation error should be fixed. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (NIFI-6489) Remove references to HipChat from website
[ https://issues.apache.org/jira/browse/NIFI-6489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-6489: Assignee: Andrew Lim > Remove references to HipChat from website > - > > Key: NIFI-6489 > URL: https://issues.apache.org/jira/browse/NIFI-6489 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > Example page: https://nifi.apache.org/mailing_lists.html -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (NIFI-6460) Remove references to HipChat in docs
[ https://issues.apache.org/jira/browse/NIFI-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893041#comment-16893041 ] Andrew Lim commented on NIFI-6460: -- NIFI-6489 filed for nifi-site repo changes. > Remove references to HipChat in docs > > > Key: NIFI-6460 > URL: https://issues.apache.org/jira/browse/NIFI-6460 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > > Example instances are in the README -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6489) Remove references to HipChat from website
Andrew Lim created NIFI-6489: Summary: Remove references to HipChat from website Key: NIFI-6489 URL: https://issues.apache.org/jira/browse/NIFI-6489 Project: Apache NiFi Issue Type: Improvement Components: Documentation Website Reporter: Andrew Lim Example page: https://nifi.apache.org/mailing_lists.html -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-6460) Remove references to HipChat in docs
[ https://issues.apache.org/jira/browse/NIFI-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-6460: - Description: Example instances are in the README (was: Example instances are in the README and [https://nifi.apache.org/mailing_lists.html]) > Remove references to HipChat in docs > > > Key: NIFI-6460 > URL: https://issues.apache.org/jira/browse/NIFI-6460 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > > Example instances are in the README -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (NIFI-6460) Remove references to HipChat in docs
[ https://issues.apache.org/jira/browse/NIFI-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16893038#comment-16893038 ] Andrew Lim commented on NIFI-6460: -- This ticket is for nifi repo changes > Remove references to HipChat in docs > > > Key: NIFI-6460 > URL: https://issues.apache.org/jira/browse/NIFI-6460 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > > Example instances are in the README and > [https://nifi.apache.org/mailing_lists.html] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (NIFI-6460) Remove references to HipChat in docs
[ https://issues.apache.org/jira/browse/NIFI-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-6460: - Summary: Remove references to HipChat in docs (was: Remove references to HipChat in Website and docs) > Remove references to HipChat in docs > > > Key: NIFI-6460 > URL: https://issues.apache.org/jira/browse/NIFI-6460 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > > Example instances are in the README and > [https://nifi.apache.org/mailing_lists.html] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFIREG-293) Highlight in Getting Started guide that only process groups can be versioned.
Andrew Lim created NIFIREG-293: -- Summary: Highlight in Getting Started guide that only process groups can be versioned. Key: NIFIREG-293 URL: https://issues.apache.org/jira/browse/NIFIREG-293 Project: NiFi Registry Issue Type: Improvement Reporter: Andrew Lim Assignee: Andrew Lim Received some feedback from new users of NiFi that only Process Groups can be versioned. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6460) Remove references to HipChat in Website and docs
Andrew Lim created NIFI-6460: Summary: Remove references to HipChat in Website and docs Key: NIFI-6460 URL: https://issues.apache.org/jira/browse/NIFI-6460 Project: Apache NiFi Issue Type: Improvement Components: Documentation Website Reporter: Andrew Lim Assignee: Andrew Lim Example instances are in the README and [https://nifi.apache.org/mailing_lists.html] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (NIFI-6457) Add section to User Guide that details how to properly move a dataflow from one NiFi instance to another
Andrew Lim created NIFI-6457:
Summary: Add section to User Guide that details how to properly
move a dataflow from one NiFi instance to another
Key: NIFI-6457
URL: https://issues.apache.org/jira/browse/NIFI-6457
Project: Apache NiFi
Issue Type: Improvement
Components: Documentation Website
Reporter: Andrew Lim
Assignee: Andrew Lim
Include how to deal with sensitive properties in processors using
{{encrypt-config}} from NiFI Toolkit
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Updated] (NIFI-6457) Add section to User Guide that details how to properly move a dataflow from one NiFi instance to another
[
https://issues.apache.org/jira/browse/NIFI-6457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Lim updated NIFI-6457:
-
Labels: security (was: )
> Add section to User Guide that details how to properly move a dataflow from
> one NiFi instance to another
>
>
> Key: NIFI-6457
> URL: https://issues.apache.org/jira/browse/NIFI-6457
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Major
> Labels: security
>
> Include how to deal with sensitive properties in processors using
> {{encrypt-config}} from NiFI Toolkit
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Reopened] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reopened NIFI-6415: -- Re-opening. Using this Jira for an addition to the README in nifi repo. I filed NIFI-6448 for a change to the Quickstart in nifi-site repo. > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Assignee: Andrew Lim >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (NIFI-6415) Nifi Build Fails on nifi-web-api
[
https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16887402#comment-16887402
]
Andrew Lim edited comment on NIFI-6415 at 7/18/19 2:16 PM:
---
Filed NIFI-6448 to add {{-DskipTests}} to Quickstart.
was (Author: andrewmlim):
File NIFI-6448 to add {{-DskipTests}} to Quickstart.
> Nifi Build Fails on nifi-web-api
>
>
> Key: NIFI-6415
> URL: https://issues.apache.org/jira/browse/NIFI-6415
> Project: Apache NiFi
> Issue Type: Bug
> Components: Documentation Website
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: David Sargrad
>Assignee: Andrew Lim
>Priority: Major
> Attachments: image-2019-07-02-14-11-15-318.png,
> image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png
>
>
> I am trying to build the latest nifi master from git.
>
> git clone [https://gitbox.apache.org/repos/asf/nifi.git]
> git checkout master
>
> I am using the command mvn install -Dmaven.test.skip=true
>
> The build consistently fails with the following message.
>
> !image-2019-07-02-14-11-15-318.png!
> I deleted my entire .m2 repository to force maven to download. I get the same
> results. Many other projects seem to build ok.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6415) Nifi Build Fails on nifi-web-api
[
https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16887402#comment-16887402
]
Andrew Lim commented on NIFI-6415:
--
File NIFI-6448 to add {{-DskipTests}} to Quickstart.
> Nifi Build Fails on nifi-web-api
>
>
> Key: NIFI-6415
> URL: https://issues.apache.org/jira/browse/NIFI-6415
> Project: Apache NiFi
> Issue Type: Bug
> Components: Documentation Website
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: David Sargrad
>Assignee: Andrew Lim
>Priority: Major
> Attachments: image-2019-07-02-14-11-15-318.png,
> image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png
>
>
> I am trying to build the latest nifi master from git.
>
> git clone [https://gitbox.apache.org/repos/asf/nifi.git]
> git checkout master
>
> I am using the command mvn install -Dmaven.test.skip=true
>
> The build consistently fails with the following message.
>
> !image-2019-07-02-14-11-15-318.png!
> I deleted my entire .m2 repository to force maven to download. I get the same
> results. Many other projects seem to build ok.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Created] (NIFI-6448) Add how to correctly skip tests during build to Quickstart guide
Andrew Lim created NIFI-6448:
Summary: Add how to correctly skip tests during build to
Quickstart guide
Key: NIFI-6448
URL: https://issues.apache.org/jira/browse/NIFI-6448
Project: Apache NiFi
Issue Type: Improvement
Components: Documentation Website
Reporter: Andrew Lim
The following was added to the README via NIFI-6415:
Execute \{{mvn clean install -DskipTests}} to compile tests, but skip running
them.
Should add to Quickstart guide for consistency.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (NIFI-6448) Add how to correctly skip tests during build to Quickstart guide
[
https://issues.apache.org/jira/browse/NIFI-6448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Lim reassigned NIFI-6448:
Assignee: Andrew Lim
> Add how to correctly skip tests during build to Quickstart guide
>
>
> Key: NIFI-6448
> URL: https://issues.apache.org/jira/browse/NIFI-6448
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Documentation Website
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> The following was added to the README via NIFI-6415:
> Execute \{{mvn clean install -DskipTests}} to compile tests, but skip running
> them.
> Should add to Quickstart guide for consistency.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Commented] (NIFI-6415) Nifi Build Fails on nifi-web-api
[
https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16887400#comment-16887400
]
Andrew Lim commented on NIFI-6415:
--
Will add the following to the README:
Execute {{mvn clean install -DskipTests}} to compile tests, but skip running
them.
> Nifi Build Fails on nifi-web-api
>
>
> Key: NIFI-6415
> URL: https://issues.apache.org/jira/browse/NIFI-6415
> Project: Apache NiFi
> Issue Type: Bug
> Components: Documentation Website
> Environment: centos 7
> mvn 3.6.0
> java 1.8.0_212 openjdk
>Reporter: David Sargrad
>Assignee: Andrew Lim
>Priority: Major
> Attachments: image-2019-07-02-14-11-15-318.png,
> image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png
>
>
> I am trying to build the latest nifi master from git.
>
> git clone [https://gitbox.apache.org/repos/asf/nifi.git]
> git checkout master
>
> I am using the command mvn install -Dmaven.test.skip=true
>
> The build consistently fails with the following message.
>
> !image-2019-07-02-14-11-15-318.png!
> I deleted my entire .m2 repository to force maven to download. I get the same
> results. Many other projects seem to build ok.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
[jira] [Assigned] (NIFI-6415) Nifi Build Fails on nifi-web-api
[ https://issues.apache.org/jira/browse/NIFI-6415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-6415: Assignee: Andrew Lim > Nifi Build Fails on nifi-web-api > > > Key: NIFI-6415 > URL: https://issues.apache.org/jira/browse/NIFI-6415 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation Website > Environment: centos 7 > mvn 3.6.0 > java 1.8.0_212 openjdk >Reporter: David Sargrad >Assignee: Andrew Lim >Priority: Major > Attachments: image-2019-07-02-14-11-15-318.png, > image-2019-07-12-12-47-58-020.png, image-2019-07-12-12-48-47-442.png > > > I am trying to build the latest nifi master from git. > > git clone [https://gitbox.apache.org/repos/asf/nifi.git] > git checkout master > > I am using the command mvn install -Dmaven.test.skip=true > > The build consistently fails with the following message. > > !image-2019-07-02-14-11-15-318.png! > I deleted my entire .m2 repository to force maven to download. I get the same > results. Many other projects seem to build ok. > > -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Comment Edited] (NIFIREG-284) Update docs for newly added granular proxy policies
[ https://issues.apache.org/jira/browse/NIFIREG-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863492#comment-16863492 ] Andrew Lim edited comment on NIFIREG-284 at 6/14/19 4:05 PM: - Per a discussion with [~bende], for 0.5.0 migration guide, should note: Existing registries will have NiFi nodes as Proxy with WRITE, so on upgrade admins will need to go in and add READ and DELETE to get them back to the same functionality they had before. For _new_ installs this is not an issue because any NiFi Identities listed in _authorizers.xml_ will be granted all three. was (Author: andrewmlim): Per a discussion with [~bende], for 0.5.0 migration guide, should note: Existing registries will have NiFi nodes as Proxy with WRITE, so on upgrade they need to go in and add READ and DELETE to get them back to the same functionality they had before For new installs it is fine because any NiFi Identities listed in _authorizers.xml_ will be granted all three. > Update docs for newly added granular proxy policies > --- > > Key: NIFIREG-284 > URL: https://issues.apache.org/jira/browse/NIFIREG-284 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > Labels: migration > > Read/write/delete policies added via NIFIREG-212 > At minimum, need to update screenshots as a result. But can also add more > information for possible use cases with these policies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFIREG-284) Update docs for newly added granular proxy policies
[ https://issues.apache.org/jira/browse/NIFIREG-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFIREG-284: --- Labels: migration (was: ) > Update docs for newly added granular proxy policies > --- > > Key: NIFIREG-284 > URL: https://issues.apache.org/jira/browse/NIFIREG-284 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > Labels: migration > > Read/write/delete policies added via NIFIREG-212 > At minimum, need to update screenshots as a result. But can also add more > information for possible use cases with these policies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFIREG-284) Update docs for newly added granular proxy policies
[ https://issues.apache.org/jira/browse/NIFIREG-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16863492#comment-16863492 ] Andrew Lim commented on NIFIREG-284: Per a discussion with [~bende], for 0.5.0 migration guide, should note: Existing registries will have NiFi nodes as Proxy with WRITE, so on upgrade they need to go in and add READ and DELETE to get them back to the same functionality they had before For new installs it is fine because any NiFi Identities listed in _authorizers.xml_ will be granted all three. > Update docs for newly added granular proxy policies > --- > > Key: NIFIREG-284 > URL: https://issues.apache.org/jira/browse/NIFIREG-284 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > > Read/write/delete policies added via NIFIREG-212 > At minimum, need to update screenshots as a result. But can also add more > information for possible use cases with these policies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-284) Update docs for newly added granular proxy policies
Andrew Lim created NIFIREG-284: -- Summary: Update docs for newly added granular proxy policies Key: NIFIREG-284 URL: https://issues.apache.org/jira/browse/NIFIREG-284 Project: NiFi Registry Issue Type: Improvement Affects Versions: 0.5.0 Reporter: Andrew Lim Read/write/delete policies added via NIFIREG-212 At minimum, need to update screenshots as a result. But can also add more information for possible use cases with these policies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFIREG-284) Update docs for newly added granular proxy policies
[ https://issues.apache.org/jira/browse/NIFIREG-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFIREG-284: -- Assignee: Andrew Lim > Update docs for newly added granular proxy policies > --- > > Key: NIFIREG-284 > URL: https://issues.apache.org/jira/browse/NIFIREG-284 > Project: NiFi Registry > Issue Type: Improvement >Affects Versions: 0.5.0 >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > > Read/write/delete policies added via NIFIREG-212 > At minimum, need to update screenshots as a result. But can also add more > information for possible use cases with these policies. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6319) Improve docs around Site-to-Site changes (URLs, batch settings, remote ports)
[ https://issues.apache.org/jira/browse/NIFI-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-6319: - Description: I noticed that there isn't any documentation for the ability to reference multiple URLs in an RPG and RPG port batch settings. New screenshots are needed and current screenshots need to be updated. (was: I noticed that there isn't any documentation for the ability to reference multiple URLs in an RPG, RPG port batch setting and remote input/output ports. New screenshots are needed and current screenshots need to be updated.) > Improve docs around Site-to-Site changes (URLs, batch settings, remote ports) > - > > Key: NIFI-6319 > URL: https://issues.apache.org/jira/browse/NIFI-6319 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > I noticed that there isn't any documentation for the ability to reference > multiple URLs in an RPG and RPG port batch settings. New screenshots are > needed and current screenshots need to be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6319) Improve docs around Site-to-Site changes (URLs, batch settings, remote ports)
[ https://issues.apache.org/jira/browse/NIFI-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-6319: - Description: I noticed that there isn't any documentation for the ability to reference multiple URLs in an RPG, RPG port batch setting and remote input/output ports. New screenshots are needed and current screenshots need to be updated. (was: I noticed that there isn't any documentation for the ability to reference multiple URLs in an RPG as well as for RPG port batch settings. Current screenshots are out of date as a result.) > Improve docs around Site-to-Site changes (URLs, batch settings, remote ports) > - > > Key: NIFI-6319 > URL: https://issues.apache.org/jira/browse/NIFI-6319 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > I noticed that there isn't any documentation for the ability to reference > multiple URLs in an RPG, RPG port batch setting and remote input/output > ports. New screenshots are needed and current screenshots need to be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6319) Improve docs around Site-to-Site changes (URLs, batch settings, remote ports)
[ https://issues.apache.org/jira/browse/NIFI-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-6319: - Summary: Improve docs around Site-to-Site changes (URLs, batch settings, remote ports) (was: Improve docs around Site-to-Site URLs and Batch Settings) > Improve docs around Site-to-Site changes (URLs, batch settings, remote ports) > - > > Key: NIFI-6319 > URL: https://issues.apache.org/jira/browse/NIFI-6319 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > I noticed that there isn't any documentation for the ability to reference > multiple URLs in an RPG as well as for RPG port batch settings. Current > screenshots are out of date as a result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-6319) Improve docs around Site-to-Site URLs and Batch Settings
[ https://issues.apache.org/jira/browse/NIFI-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16847631#comment-16847631 ] Andrew Lim commented on NIFI-6319: -- Will also make some readability edits to the doc added for NIFI-2933 Remote input/output ports at any PG. > Improve docs around Site-to-Site URLs and Batch Settings > > > Key: NIFI-6319 > URL: https://issues.apache.org/jira/browse/NIFI-6319 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > I noticed that there isn't any documentation for the ability to reference > multiple URLs in an RPG as well as for RPG port batch settings. Current > screenshots are out of date as a result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6319) Improve docs around Site-to-Site URLs and Batch Settings
[ https://issues.apache.org/jira/browse/NIFI-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-6319: - Description: I noticed that there isn't any documentation for the ability to reference multiple URLs in an RPG as well as for RPG port batch settings. Current screenshots are out of date as a result. (was: I noticed that there isn't any documentation for the ability to reference multiple URLs in an RPG as well as for RPG port batch settings.) > Improve docs around Site-to-Site URLs and Batch Settings > > > Key: NIFI-6319 > URL: https://issues.apache.org/jira/browse/NIFI-6319 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > I noticed that there isn't any documentation for the ability to reference > multiple URLs in an RPG as well as for RPG port batch settings. Current > screenshots are out of date as a result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6319) Improve docs around Site-to-Site URLs and Batch Settings
Andrew Lim created NIFI-6319: Summary: Improve docs around Site-to-Site URLs and Batch Settings Key: NIFI-6319 URL: https://issues.apache.org/jira/browse/NIFI-6319 Project: Apache NiFi Issue Type: Improvement Components: Documentation Website Reporter: Andrew Lim Assignee: Andrew Lim I noticed that there isn't any documentation for the ability to reference multiple URLs in an RPG as well as for RPG port batch settings. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-271) Enable automated UI tests to run during build without requiring separate instance of Registry
Andrew Lim created NIFIREG-271: -- Summary: Enable automated UI tests to run during build without requiring separate instance of Registry Key: NIFIREG-271 URL: https://issues.apache.org/jira/browse/NIFIREG-271 Project: NiFi Registry Issue Type: Improvement Reporter: Andrew Lim Selenium tests currently require a separate unsecured registry instance running on a hardcoded port (default port of 18080). Improve the test infrastructure to not have this requirement leveraging the test automation that exists for API tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFIREG-271) Enable automated UI tests to run during build without requiring separate instance of Registry
[ https://issues.apache.org/jira/browse/NIFIREG-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFIREG-271: -- Assignee: Andrew Lim > Enable automated UI tests to run during build without requiring separate > instance of Registry > - > > Key: NIFIREG-271 > URL: https://issues.apache.org/jira/browse/NIFIREG-271 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > > Selenium tests currently require a separate unsecured registry instance > running on a hardcoded port (default port of 18080). > Improve the test infrastructure to not have this requirement leveraging the > test automation that exists for API tests. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFIREG-270) Add additional UI automation for User test cases
[ https://issues.apache.org/jira/browse/NIFIREG-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFIREG-270: -- Assignee: Andrew Lim > Add additional UI automation for User test cases > > > Key: NIFIREG-270 > URL: https://issues.apache.org/jira/browse/NIFIREG-270 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > > Add Selenium tests for user creation, deletion, renaming, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-270) Add additional UI automation for User test cases
Andrew Lim created NIFIREG-270: -- Summary: Add additional UI automation for User test cases Key: NIFIREG-270 URL: https://issues.apache.org/jira/browse/NIFIREG-270 Project: NiFi Registry Issue Type: Improvement Reporter: Andrew Lim Add Selenium tests for user creation, deletion, renaming, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFIREG-266) Introduce automated UI testing
[
https://issues.apache.org/jira/browse/NIFIREG-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16836458#comment-16836458
]
Andrew Lim commented on NIFIREG-266:
Just wanted to note that the tests run explicitly with the following build
command referencing a selenium test profile:
{{mvn install -Pselenium_tests}}
Additionally, the following are required:
-an unsecured Registry instance running on the default port of 18080
-Chrome browser since the tests use the Selenium ChromeDriver
The initial tests cover bucket use cases (creating buckets, deleting buckets,
renaming buckets, canceling bucket creation and deletion, duplicating bucket
names).
> Introduce automated UI testing
> --
>
> Key: NIFIREG-266
> URL: https://issues.apache.org/jira/browse/NIFIREG-266
> Project: NiFi Registry
> Issue Type: Task
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Major
> Fix For: 0.4.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (NIFIREG-269) Docs link should be "REST API" not "Rest Api"
[ https://issues.apache.org/jira/browse/NIFIREG-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFIREG-269: -- Assignee: Andrew Lim > Docs link should be "REST API" not "Rest Api" > - > > Key: NIFIREG-269 > URL: https://issues.apache.org/jira/browse/NIFIREG-269 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Trivial > > Similar to https://issues.apache.org/jira/browse/NIFI-6002, REST API is an > acronym so it should be capitalized. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-269) Docs link should be "REST API" not "Rest Api"
Andrew Lim created NIFIREG-269: -- Summary: Docs link should be "REST API" not "Rest Api" Key: NIFIREG-269 URL: https://issues.apache.org/jira/browse/NIFIREG-269 Project: NiFi Registry Issue Type: Improvement Reporter: Andrew Lim Similar to https://issues.apache.org/jira/browse/NIFI-6002, REST API is an acronym so it should be capitalized. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-6267) Expression Language Guide has errors for replaceAll
Andrew Lim created NIFI-6267: Summary: Expression Language Guide has errors for replaceAll Key: NIFI-6267 URL: https://issues.apache.org/jira/browse/NIFI-6267 Project: Apache NiFi Issue Type: Bug Components: Documentation Website Reporter: Andrew Lim [https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#replaceall] Arguments is listed twice and "Regex: he Regular Expression..." should be "Regex: *T*he Regular Expression..." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFIREG-266) Introduce automated UI testing
[ https://issues.apache.org/jira/browse/NIFIREG-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFIREG-266: -- Assignee: Andrew Lim > Introduce automated UI testing > -- > > Key: NIFIREG-266 > URL: https://issues.apache.org/jira/browse/NIFIREG-266 > Project: NiFi Registry > Issue Type: Task >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-266) Introduce automated UI testing
Andrew Lim created NIFIREG-266: -- Summary: Introduce automated UI testing Key: NIFIREG-266 URL: https://issues.apache.org/jira/browse/NIFIREG-266 Project: NiFi Registry Issue Type: Task Reporter: Andrew Lim -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFIREG-263) Update HTML ids added for testing to be more explicit about their purpose
[ https://issues.apache.org/jira/browse/NIFIREG-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFIREG-263: --- Description: HTML ids were added in https://issues.apache.org/jira/browse/NIFIREG-56 and https://issues.apache.org/jira/browse/NIFIREG-185 for testing/automation purposes. To avoid confusion, suggest we change these references from "id" to "data-automation-id" was: HTML Iids were added in https://issues.apache.org/jira/browse/NIFIREG-56 and https://issues.apache.org/jira/browse/NIFIREG-185 for testing/automation purposes. To avoid confusion, suggest we change these references from "id" to "data-automation-id" > Update HTML ids added for testing to be more explicit about their purpose > - > > Key: NIFIREG-263 > URL: https://issues.apache.org/jira/browse/NIFIREG-263 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > HTML ids were added in https://issues.apache.org/jira/browse/NIFIREG-56 and > https://issues.apache.org/jira/browse/NIFIREG-185 for testing/automation > purposes. > To avoid confusion, suggest we change these references from "id" to > "data-automation-id" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFIREG-263) Update HTML ids added for testing to be more explicit about their purpose
[ https://issues.apache.org/jira/browse/NIFIREG-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16832132#comment-16832132 ] Andrew Lim commented on NIFIREG-263: Planning on referencing these data-automation-ids in some Selenium automation I am writing > Update HTML ids added for testing to be more explicit about their purpose > - > > Key: NIFIREG-263 > URL: https://issues.apache.org/jira/browse/NIFIREG-263 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > HTML Iids were added in https://issues.apache.org/jira/browse/NIFIREG-56 and > https://issues.apache.org/jira/browse/NIFIREG-185 for testing/automation > purposes. > To avoid confusion, suggest we change these references from "id" to > "data-automation-id" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFIREG-263) Update HTML ids added for testing to be more explicit about their purpose
[ https://issues.apache.org/jira/browse/NIFIREG-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFIREG-263: --- Description: HTML Iids were added in https://issues.apache.org/jira/browse/NIFIREG-56 and https://issues.apache.org/jira/browse/NIFIREG-185 for testing/automation purposes. To avoid confusion, suggest we change these references from "id" to "data-automation-id" was: Ids were added in https://issues.apache.org/jira/browse/NIFIREG-56 and https://issues.apache.org/jira/browse/NIFIREG-185 for testing/automation purposes. To avoid confusion, suggest we change these references from "id" to "data-automation-id" > Update HTML ids added for testing to be more explicit about their purpose > - > > Key: NIFIREG-263 > URL: https://issues.apache.org/jira/browse/NIFIREG-263 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > HTML Iids were added in https://issues.apache.org/jira/browse/NIFIREG-56 and > https://issues.apache.org/jira/browse/NIFIREG-185 for testing/automation > purposes. > To avoid confusion, suggest we change these references from "id" to > "data-automation-id" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFIREG-263) Update HTML ids added for testing to be more explicit about their purpose
[ https://issues.apache.org/jira/browse/NIFIREG-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFIREG-263: --- Summary: Update HTML ids added for testing to be more explicit about their purpose (was: Update ids added for testing to be more explicit about their purpose) > Update HTML ids added for testing to be more explicit about their purpose > - > > Key: NIFIREG-263 > URL: https://issues.apache.org/jira/browse/NIFIREG-263 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > Ids were added in https://issues.apache.org/jira/browse/NIFIREG-56 and > https://issues.apache.org/jira/browse/NIFIREG-185 for testing/automation > purposes. > To avoid confusion, suggest we change these references from "id" to > "data-automation-id" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-263) Update ids added for testing to be more explicit about their purpose
Andrew Lim created NIFIREG-263: -- Summary: Update ids added for testing to be more explicit about their purpose Key: NIFIREG-263 URL: https://issues.apache.org/jira/browse/NIFIREG-263 Project: NiFi Registry Issue Type: Improvement Reporter: Andrew Lim Ids were added in https://issues.apache.org/jira/browse/NIFIREG-56 and https://issues.apache.org/jira/browse/NIFIREG-185 for testing/automation purposes. To avoid confusion, suggest we change these references from "id" to "data-automation-id" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFIREG-263) Update ids added for testing to be more explicit about their purpose
[ https://issues.apache.org/jira/browse/NIFIREG-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFIREG-263: -- Assignee: Andrew Lim > Update ids added for testing to be more explicit about their purpose > > > Key: NIFIREG-263 > URL: https://issues.apache.org/jira/browse/NIFIREG-263 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > Ids were added in https://issues.apache.org/jira/browse/NIFIREG-56 and > https://issues.apache.org/jira/browse/NIFIREG-185 for testing/automation > purposes. > To avoid confusion, suggest we change these references from "id" to > "data-automation-id" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFIREG-259) Edits to Admin Guide for content related to persistence provider, credentials provider, event types and metadata database
[ https://issues.apache.org/jira/browse/NIFIREG-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16827237#comment-16827237 ] Andrew Lim commented on NIFIREG-259: [https://github.com/apache/nifi-registry/pull/176] > Edits to Admin Guide for content related to persistence provider, credentials > provider, event types and metadata database > - > > Key: NIFIREG-259 > URL: https://issues.apache.org/jira/browse/NIFIREG-259 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > Time Spent: 10m > Remaining Estimate: 0h > > Reviewed the great new content added to the Admin Guide as part of > https://issues.apache.org/jira/browse/NIFIREG-244 and found some places to > edit for improved readability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-259) Edits to Admin Guide for content related to persistence provider, credentials provider, event types and metadata database
Andrew Lim created NIFIREG-259: -- Summary: Edits to Admin Guide for content related to persistence provider, credentials provider, event types and metadata database Key: NIFIREG-259 URL: https://issues.apache.org/jira/browse/NIFIREG-259 Project: NiFi Registry Issue Type: Improvement Reporter: Andrew Lim Reviewed the great new content added to the Admin Guide as part of https://issues.apache.org/jira/browse/NIFIREG-244 and found some places to edit for improved readability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFIREG-259) Edits to Admin Guide for content related to persistence provider, credentials provider, event types and metadata database
[ https://issues.apache.org/jira/browse/NIFIREG-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFIREG-259: -- Assignee: Andrew Lim > Edits to Admin Guide for content related to persistence provider, credentials > provider, event types and metadata database > - > > Key: NIFIREG-259 > URL: https://issues.apache.org/jira/browse/NIFIREG-259 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > > Reviewed the great new content added to the Admin Guide as part of > https://issues.apache.org/jira/browse/NIFIREG-244 and found some places to > edit for improved readability. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-258) UI: Allow changes to bucket and user name to be saved automatically
Andrew Lim created NIFIREG-258: -- Summary: UI: Allow changes to bucket and user name to be saved automatically Key: NIFIREG-258 URL: https://issues.apache.org/jira/browse/NIFIREG-258 Project: NiFi Registry Issue Type: Improvement Reporter: Andrew Lim In the User configuration sidenav, changes to Special Privileges are automatically saved, expediting the modification process. After discussions with [~rmoran], we could do something similar for changes to both the User Name in the same window and Bucket Name in the Bucket config sidenav. Here is the envisioned workflow: # Bucket/User name is changed. # If the user selects Return on the keyboard, the change is saved. Alternatively, if the user clicks out of the name field and changes focus, the change is saved. # The Success toaster message is displayed. If this scenario is implemented, the Save button can be removed from the UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFIREG-257) UI: When Special Privileges changes are made, user should get acknowledgement that those changes have been automatically saved.
[ https://issues.apache.org/jira/browse/NIFIREG-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFIREG-257: --- Description: Current behavior in the User configuration sidenav, is that when any of the Special Privileges checkboxes are selected, they are automatically saved. But the user gets no feedback from the app that this happens. Other changes in this window (changing the user name or adding the user to a group) prompts a Success toaster message. We should do the same for special privileges changes. Suggested message text: Special privileges for this user have been updated. was: Current behavior in the User configuration sidenav, is that when any of the Special Privileges checkboxes are selected, they are automatically saved. But the user gets no feedback from the app that this happens. Other changes in this window (changing the user name or adding the user to a group) prompts a Success toaster message. We should do the same for special privileges changes. Suggested message text: Special privileges for this user name have been updated. > UI: When Special Privileges changes are made, user should get acknowledgement > that those changes have been automatically saved. > --- > > Key: NIFIREG-257 > URL: https://issues.apache.org/jira/browse/NIFIREG-257 > Project: NiFi Registry > Issue Type: Improvement >Reporter: Andrew Lim >Priority: Major > > Current behavior in the User configuration sidenav, is that when any of the > Special Privileges checkboxes are selected, they are automatically saved. > But the user gets no feedback from the app that this happens. Other changes > in this window (changing the user name or adding the user to a group) prompts > a Success toaster message. We should do the same for special privileges > changes. Suggested message text: > Special privileges for this user have been updated. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFIREG-257) UI: When Special Privileges changes are made, user should get acknowledgement that those changes have been automatically saved.
Andrew Lim created NIFIREG-257: -- Summary: UI: When Special Privileges changes are made, user should get acknowledgement that those changes have been automatically saved. Key: NIFIREG-257 URL: https://issues.apache.org/jira/browse/NIFIREG-257 Project: NiFi Registry Issue Type: Improvement Reporter: Andrew Lim Current behavior in the User configuration sidenav, is that when any of the Special Privileges checkboxes are selected, they are automatically saved. But the user gets no feedback from the app that this happens. Other changes in this window (changing the user name or adding the user to a group) prompts a Success toaster message. We should do the same for special privileges changes. Suggested message text: Special privileges for this user name have been updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFI-6002) Fix formatting on docs links
[ https://issues.apache.org/jira/browse/NIFI-6002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-6002: Assignee: Andrew Lim > Fix formatting on docs links > > > Key: NIFI-6002 > URL: https://issues.apache.org/jira/browse/NIFI-6002 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Affects Versions: 1.8.0 >Reporter: Andy LoPresto >Assignee: Andrew Lim >Priority: Trivial > Labels: beginner, documentation, html > > When reviewing NIFI-5990, I noticed some link CSS classes were probably > duplicated via copy/paste, and the display value for "Rest Api" should be > "REST API" as those are both acronyms. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-6176) Improve description for nifi.cluster.load.balance.max.thread.count property in Admin Guide
[ https://issues.apache.org/jira/browse/NIFI-6176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim updated NIFI-6176: - Fix Version/s: 1.10.0 > Improve description for nifi.cluster.load.balance.max.thread.count property > in Admin Guide > -- > > Key: NIFI-6176 > URL: https://issues.apache.org/jira/browse/NIFI-6176 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Andrew Lim >Assignee: Andrew Lim >Priority: Minor > Fix For: 1.10.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Discussed ways to improve the current property description with [~markap14] > and came up with the following: > > The maximum number of threads to use for transferring data from this node to > other nodes in the cluster. While a given thread can only write to a single > socket at a time, a single thread is capable of servicing multiple > connections simultaneously because a given connection may not be available > for reading/writing at any given time. The default value is 8—i.e., up to 8 > threads will be responsible for transferring data to other nodes, regardless > of how many nodes are in the cluster. > > *NOTE:* Increasing this value will allow additional threads to be used for > communicating with other nodes in the cluster and writing the data to the > Content and FlowFile Repositories. However, if this property is set to a > value greater than the number of nodes in the cluster multiplied by the > number of connections per node > (nifi.cluster.load.balance.connections.per.node), then no further benefit > will be gained and resources will be wasted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5793) Remove CLI README for NiFi 1.10
[ https://issues.apache.org/jira/browse/NIFI-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821520#comment-16821520 ] Andrew Lim commented on NIFI-5793: -- 1.9.0 was released in February 2019. > Remove CLI README for NiFi 1.10 > --- > > Key: NIFI-5793 > URL: https://issues.apache.org/jira/browse/NIFI-5793 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Affects Versions: 1.9.0 >Reporter: Pierre Villard >Assignee: Andrew Lim >Priority: Major > > With NIFI-5767 we added a dedicated documentation page for the toolkit. We > don't need the CLI README anymore and should be removed for NiFi 1.10 (once > NiFi 1.9.0 is released). > https://github.com/apache/nifi/blob/master/nifi-toolkit/nifi-toolkit-cli/README.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFI-5793) Remove CLI README for NiFi 1.10
[ https://issues.apache.org/jira/browse/NIFI-5793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Lim reassigned NIFI-5793: Assignee: Andrew Lim > Remove CLI README for NiFi 1.10 > --- > > Key: NIFI-5793 > URL: https://issues.apache.org/jira/browse/NIFI-5793 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Affects Versions: 1.9.0 >Reporter: Pierre Villard >Assignee: Andrew Lim >Priority: Major > > With NIFI-5767 we added a dedicated documentation page for the toolkit. We > don't need the CLI README anymore and should be removed for NiFi 1.10 (once > NiFi 1.9.0 is released). > https://github.com/apache/nifi/blob/master/nifi-toolkit/nifi-toolkit-cli/README.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFI-6205) Improve error messages if value entered for Concurrent Tasks on input/output ports is too large
[
https://issues.apache.org/jira/browse/NIFI-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Lim reassigned NIFI-6205:
Assignee: (was: Andrew Lim)
> Improve error messages if value entered for Concurrent Tasks on input/output
> ports is too large
>
>
> Key: NIFI-6205
> URL: https://issues.apache.org/jira/browse/NIFI-6205
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Andrew Lim
>Priority: Minor
>
> When modifying the Concurrent Tasks on an Input/Output port by adding a very
> large integer, I see these two errors:
> * Cannot deserialize value of type {{java.lang.Integer}} from String
> "123123123123": Overflow: numeric value (123123123123) out of range of
> Integer (-2147483648 - 2147483647)
> * at [Source:
> (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream);
> line: 1, column: 231] (through reference chain:
> org.apache.nifi.web.api.entity.PortEntity["component"]->org.apache.nifi.web.api.dto.PortDTO["concurrentlySchedulableTaskCount"])
> We should improve the error messages to be more user-friendly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (NIFI-6205) Improve error messages if value entered for Concurrent Tasks on input/output ports is too large
[
https://issues.apache.org/jira/browse/NIFI-6205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Lim updated NIFI-6205:
-
Summary: Improve error messages if value entered for Concurrent Tasks on
input/output ports is too large (was: Improve error messages if value entered
for Concurrent Tasks on input/output ports are too large )
> Improve error messages if value entered for Concurrent Tasks on input/output
> ports is too large
>
>
> Key: NIFI-6205
> URL: https://issues.apache.org/jira/browse/NIFI-6205
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> When modifying the Concurrent Tasks on an Input/Output port by adding a very
> large integer, I see these two errors:
> * Cannot deserialize value of type {{java.lang.Integer}} from String
> "123123123123": Overflow: numeric value (123123123123) out of range of
> Integer (-2147483648 - 2147483647)
> * at [Source:
> (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream);
> line: 1, column: 231] (through reference chain:
> org.apache.nifi.web.api.entity.PortEntity["component"]->org.apache.nifi.web.api.dto.PortDTO["concurrentlySchedulableTaskCount"])
> We should improve the error messages to be more user-friendly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
