[jira] [Created] (NIFI-2183) Remove DownloadSvg servlet
Matt Gilman created NIFI-2183: - Summary: Remove DownloadSvg servlet Key: NIFI-2183 URL: https://issues.apache.org/jira/browse/NIFI-2183 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Matt Gilman Assignee: Matt Gilman Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2167) Disabled state not including in a Processor that was copy/paste
Matt Gilman created NIFI-2167: - Summary: Disabled state not including in a Processor that was copy/paste Key: NIFI-2167 URL: https://issues.apache.org/jira/browse/NIFI-2167 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Matt Gilman Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-1563) Remove storage of components' stats and bulletins from NCM
[ https://issues.apache.org/jira/browse/NIFI-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-1563. --- Resolution: Fixed Yep, I think this has been resolved. Thanks [~markap14] > Remove storage of components' stats and bulletins from NCM > -- > > Key: NIFI-1563 > URL: https://issues.apache.org/jira/browse/NIFI-1563 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Mark Payne >Assignee: Mark Payne > Fix For: 1.0.0 > > Original Estimate: 168h > Remaining Estimate: 168h > > Currently, each node in a cluster sends a period heartbeat that contains the > stats for all components in the node. This happens every 5 seconds by > default. This results in quite a lot of chatter between the NCM and nodes. It > made sense to take this approach when the clustering concept was designed > because there were no Process Groups, and we had no notion of merging > responses from nodes for a web request. > However, now we should replicate the request to all nodes and then merge the > responses on demand, rather than storing this information on the NCM. This > requires far less bandwidth because we only need to pull the stats for a > particular Process Group and only on demand instead of every 5 seconds. > Additionally, this is laying groundwork for the Zero-Master clustering that > we want to have in place for 1.0.0. > In order to remove the stats from the NCM, we will also need to remove the > bulletins and stats history. These requests will all need to be federated and > the responses merged on-demand. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-906) Docs do not display well on mobile/smaller res devices
[ https://issues.apache.org/jira/browse/NIFI-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356193#comment-15356193 ] Matt Gilman commented on NIFI-906: -- [~ijokarumawak] Thanks for jumping into this! Your correct, the website is built using Foundation. The ‘NiFi Docs’ on the website are generated by NiFi during startup and has to be manually deployed to the website after a release. I think you’re on the right track that we just want to use some modern CSS to get the behavior we want. I don’t think we want to start bundling Foundation (or some other framework) in the NiFi assembly just to get responsive documentation. Some simple CSS should give us want we want. > Docs do not display well on mobile/smaller res devices > -- > > Key: NIFI-906 > URL: https://issues.apache.org/jira/browse/NIFI-906 > Project: Apache NiFi > Issue Type: Bug > Components: Documentation & Website > Environment: Mobile, Small res devices >Reporter: Joseph Witt > > Tweet from @cyroxx > @apachenifi Unfortunately, the docs (http://nifi.apache.org/docs.html ) are > not mobile-friendly, makes it hard to read about this interesting project > https://twitter.com/cyroxx/status/637305973938483200 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (NIFI-2132) New scheduler slider
[ https://issues.apache.org/jira/browse/NIFI-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352882#comment-15352882 ] Matt Gilman edited comment on NIFI-2132 at 6/28/16 12:10 PM: - Should also include the Provenance Timestamp slider in the lineage view. was (Author: mcgilman): Should also include the Provenance Timestamp slider. > New scheduler slider > > > Key: NIFI-2132 > URL: https://issues.apache.org/jira/browse/NIFI-2132 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Scott Aslan > > scheduler slider need refresh -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2132) New scheduler slider
[ https://issues.apache.org/jira/browse/NIFI-2132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15352882#comment-15352882 ] Matt Gilman commented on NIFI-2132: --- Should also include the Provenance Timestamp slider. > New scheduler slider > > > Key: NIFI-2132 > URL: https://issues.apache.org/jira/browse/NIFI-2132 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Scott Aslan > > scheduler slider need refresh -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2127) Authorizer - Create populated User Group
Matt Gilman created NIFI-2127: - Summary: Authorizer - Create populated User Group Key: NIFI-2127 URL: https://issues.apache.org/jira/browse/NIFI-2127 Project: Apache NiFi Issue Type: Bug Components: Core Framework, Extensions Reporter: Matt Gilman Assignee: Bryan Bende Fix For: 1.0.0 Unable to create a Group populated with users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-1740) Unable to view content when of unknown type
[ https://issues.apache.org/jira/browse/NIFI-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-1740. --- Resolution: Duplicate Fix Version/s: 0.7.0 > Unable to view content when of unknown type > --- > > Key: NIFI-1740 > URL: https://issues.apache.org/jira/browse/NIFI-1740 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Reporter: Mark Payne >Assignee: Matt Gilman > Fix For: 0.7.0 > > > I have a GenerateFlowFile -> UpdateAttribute. > I queued up some data in the queue and clicked List Queue. When I then try to > view the content of the FlowFile, the dialog that pops up shows the dropdown > for "View as" with no options. > Opening Chrome's Developer Tools, I see the following error: > nf-ajax-setup.js:1 > Uncaught TypeError: Cannot read property 'ajaxSetup' of undefined > (anonymous function) @ nf-ajax-setup.js:1 > j @ jquery-2.1.1.min.js:2 > k.fireWith @ jquery-2.1.1.min.js:2 > n.extend.ready @ jquery-2.1.1.min.js:2 > I @ jquery-2.1.1.min.js:2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-1564) Content Viewer - Issue when there is no supported viewer
[ https://issues.apache.org/jira/browse/NIFI-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-1564. --- Resolution: Fixed Assignee: Matt Gilman Fix Version/s: 0.7.0 > Content Viewer - Issue when there is no supported viewer > > > Key: NIFI-1564 > URL: https://issues.apache.org/jira/browse/NIFI-1564 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Trivial > Fix For: 0.7.0 > > > When there is no supported viewer for a given content type, the button that > allows the viewer to switch between Original, Formatted, and Hex does not > render correctly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2122) Users, Groups, Policies API handling of unsecure request
Matt Gilman created NIFI-2122: - Summary: Users, Groups, Policies API handling of unsecure request Key: NIFI-2122 URL: https://issues.apache.org/jira/browse/NIFI-2122 Project: Apache NiFi Issue Type: Sub-task Components: Core Framework Reporter: Matt Gilman Priority: Minor Fix For: 1.0.0 When the users, groups, or policies endpoint receives an unsecure request we should fail fast likely with an IllegalStateException as using the users, groups, and policies endpoints require HTTPS. Only HTTP the user is always authenticated as an anonymous user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2093) Clear state link on Component State window is hidden
[ https://issues.apache.org/jira/browse/NIFI-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347531#comment-15347531 ] Matt Gilman commented on NIFI-2093: --- [~ijokarumawak] Perfect! That's all I wanted to verify. So I think the z-index change which you incorporated into PR-563 should be all we need here. Thanks! > Clear state link on Component State window is hidden > > > Key: NIFI-2093 > URL: https://issues.apache.org/jira/browse/NIFI-2093 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Koji Kawamura >Assignee: Koji Kawamura > Fix For: 1.0.0 > > Attachments: ComponentState-ConsumeKafka.png > > > It seems that ComponentStateEntity should have accessPolicy so that > CanvasUtis.supportsModification() can handle whether the link is active or > not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2102) Queue Viewer Refresh
[ https://issues.apache.org/jira/browse/NIFI-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2102. --- Resolution: Duplicate > Queue Viewer Refresh > > > Key: NIFI-2102 > URL: https://issues.apache.org/jira/browse/NIFI-2102 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman > Fix For: 1.0.0 > > > Sure queue viewer and all associated dialogs are properly styled. Include > FlowFile details, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2102) Queue Viewer Refresh
Matt Gilman created NIFI-2102: - Summary: Queue Viewer Refresh Key: NIFI-2102 URL: https://issues.apache.org/jira/browse/NIFI-2102 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Fix For: 1.0.0 Sure queue viewer and all associated dialogs are properly styled. Include FlowFile details, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2059) Secure cluster request replication
[ https://issues.apache.org/jira/browse/NIFI-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2059: -- Assignee: Mark Payne > Secure cluster request replication > -- > > Key: NIFI-2059 > URL: https://issues.apache.org/jira/browse/NIFI-2059 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.0.0 > > > I attempted to stand up a secure cluster and was having issues with request > replication. It appears that with the current approach every node will need > to authorize every other node as a proxy and we need to ensure those requests > are being replicated on behalf of the end user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2059) Secure cluster request replication
[ https://issues.apache.org/jira/browse/NIFI-2059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2059. --- Resolution: Fixed > Secure cluster request replication > -- > > Key: NIFI-2059 > URL: https://issues.apache.org/jira/browse/NIFI-2059 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.0.0 > > > I attempted to stand up a secure cluster and was having issues with request > replication. It appears that with the current approach every node will need > to authorize every other node as a proxy and we need to ensure those requests > are being replicated on behalf of the end user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2044) Require revision for component creation
[ https://issues.apache.org/jira/browse/NIFI-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2044: -- Description: - When creating a component, require the revision to be specified to ensure we're using the appropriate client id. - Require component exists for PUT requests. was: - When creating a component, require the revision to be specified to ensure we're using the appropriate client id. - Perform proper authorization when components are created via PUT. > Require revision for component creation > --- > > Key: NIFI-2044 > URL: https://issues.apache.org/jira/browse/NIFI-2044 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > - When creating a component, require the revision to be specified to ensure > we're using the appropriate client id. > - Require component exists for PUT requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2095) Introduce UI for managing Users & User Groups
[ https://issues.apache.org/jira/browse/NIFI-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2095: -- Issue Type: Sub-task (was: Improvement) Parent: NIFI-1550 > Introduce UI for managing Users & User Groups > - > > Key: NIFI-2095 > URL: https://issues.apache.org/jira/browse/NIFI-2095 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Blocker > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2095) Introduce UI for managing Users & User Groups
Matt Gilman created NIFI-2095: - Summary: Introduce UI for managing Users & User Groups Key: NIFI-2095 URL: https://issues.apache.org/jira/browse/NIFI-2095 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Priority: Blocker Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-2044) Require revision for component creation
[ https://issues.apache.org/jira/browse/NIFI-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-2044: - Assignee: Matt Gilman > Require revision for component creation > --- > > Key: NIFI-2044 > URL: https://issues.apache.org/jira/browse/NIFI-2044 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > - When creating a component, require the revision to be specified to ensure > we're using the appropriate client id. > - Perform proper authorization when components are created via PUT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (NIFI-2093) Clear state link on Component State window is hidden
[ https://issues.apache.org/jira/browse/NIFI-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346335#comment-15346335 ] Matt Gilman edited comment on NIFI-2093 at 6/23/16 12:25 PM: - [~ijokarumawak] I was referring to client side. Whether the Clear link is activate or not is based on a flag passed into the showState function in nf-component-state.js. If you look where this is called from we already account for the access controls for Processors via calling supportsModification. However, I didn't notice a comparable check for Controller Services and Reporting Tasks. What's there may be ok if we're already checking the access controls prior to that point but its something that I wanted to make sure was re-visited. I believe the check on the server side is accurate. In our 0.x baseline, viewing and clearing state are actions that are reserved for a Data Flow Manager. Meaning that read only users are not allowed to view or clear state. In our new component based access model, that would equate to requiring WRITE access for the component. I think we made the decision on requiring DFM role in 0.x because state is a very low level concept and not something that a MONITOR user should be concerned with. was (Author: mcgilman): [~ijokarumawak] I was referring to client side. Whether the Clear link is activate or not is based on a flag passed into the showState function in nf-component-state.js. If you look where this is called from we already account for the access controls for Processors via calling supportsModification. However, I didn't notice a comparable check for Controller Services and Reporting Tasks. I believe the check on the server side is accurate. In our 0.x baseline, viewing and clearing state are actions that are reserved for a Data Flow Manager. Meaning that read only users are not allowed to view or clear state. In our new component based access model, that would equate to requiring WRITE access for the component. I think we made the decision on requiring DFM role in 0.x because state is a very low level concept and not something that a MONITOR user should be concerned with. > Clear state link on Component State window is hidden > > > Key: NIFI-2093 > URL: https://issues.apache.org/jira/browse/NIFI-2093 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Koji Kawamura >Assignee: Koji Kawamura > Fix For: 1.0.0 > > Attachments: ComponentState-ConsumeKafka.png > > > It seems that ComponentStateEntity should have accessPolicy so that > CanvasUtis.supportsModification() can handle whether the link is active or > not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2093) Clear state link on Component State window is hidden
[ https://issues.apache.org/jira/browse/NIFI-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346335#comment-15346335 ] Matt Gilman commented on NIFI-2093: --- [~ijokarumawak] I was referring to client side. Whether the Clear link is activate or not is based on a flag passed into the showState function in nf-component-state.js. If you look where this is called from we already account for the access controls for Processors via calling supportsModification. However, I didn't notice a comparable check for Controller Services and Reporting Tasks. I believe the check on the server side is accurate. In our 0.x baseline, viewing and clearing state are actions that are reserved for a Data Flow Manager. Meaning that read only users are not allowed to view or clear state. In our new component based access model, that would equate to requiring WRITE access for the component. I think we made the decision on requiring DFM role in 0.x because state is a very low level concept and not something that a MONITOR user should be concerned with. > Clear state link on Component State window is hidden > > > Key: NIFI-2093 > URL: https://issues.apache.org/jira/browse/NIFI-2093 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Koji Kawamura >Assignee: Koji Kawamura > Fix For: 1.0.0 > > Attachments: ComponentState-ConsumeKafka.png > > > It seems that ComponentStateEntity should have accessPolicy so that > CanvasUtis.supportsModification() can handle whether the link is active or > not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-2093) Clear state link on Component State window is disabled
[ https://issues.apache.org/jira/browse/NIFI-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15345670#comment-15345670 ] Matt Gilman commented on NIFI-2093: --- After a quick glance it appears the clear link is hidden behind the button container in the dialog. It's enabled/disabled state appears to be correct for Processors. However we need to ensure that we're taking into account the access policies of the source component for Controller Services and Reporting Tasks. > Clear state link on Component State window is disabled > -- > > Key: NIFI-2093 > URL: https://issues.apache.org/jira/browse/NIFI-2093 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Koji Kawamura > Attachments: ComponentState-ConsumeKafka.png > > > It seems that ComponentStateEntity should have accessPolicy so that > CanvasUtis.supportsModification() can handle whether the link is active or > not. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2044) Require revision for component creation
[ https://issues.apache.org/jira/browse/NIFI-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2044: -- Description: - When creating a component, require the revision to be specified to ensure we're using the appropriate client id. - Perform proper authorization when components are created via PUT. was: - When creating a component, require the revision to be specified to ensure we're using the appropriate client id. - Require component exists for PUT requests. > Require revision for component creation > --- > > Key: NIFI-2044 > URL: https://issues.apache.org/jira/browse/NIFI-2044 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Core UI >Reporter: Matt Gilman > Fix For: 1.0.0 > > > - When creating a component, require the revision to be specified to ensure > we're using the appropriate client id. > - Perform proper authorization when components are created via PUT. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2077) Remove old 0.x images that have been replaced in 1.x
Matt Gilman created NIFI-2077: - Summary: Remove old 0.x images that have been replaced in 1.x Key: NIFI-2077 URL: https://issues.apache.org/jira/browse/NIFI-2077 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Priority: Minor Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1946) UI - Palette's
[ https://issues.apache.org/jira/browse/NIFI-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342705#comment-15342705 ] Matt Gilman commented on NIFI-1946: --- While testing ran into an issue in the provenance page. Created a corresponding JIRA: https://issues.apache.org/jira/browse/NIFI-2075 > UI - Palette's > -- > > Key: NIFI-1946 > URL: https://issues.apache.org/jira/browse/NIFI-1946 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > Attachments: 0001-NIFI-1946.patch > > > - Expand by default > - Align palette handles in the top left of the canvas -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2076) New Inline Controller Service Dialog
Matt Gilman created NIFI-2076: - Summary: New Inline Controller Service Dialog Key: NIFI-2076 URL: https://issues.apache.org/jira/browse/NIFI-2076 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Fix For: 1.0.0 - is too wide -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2027) Properties Tables
[ https://issues.apache.org/jira/browse/NIFI-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2027: -- Description: - Non-EL Property editor, cannot resize horizontally - EL Property editor, resize renders too slowly - Is empty check box positioning is off - window resize event needs to resize any visible properties tables - Property table heights are too short - GoTo icon is right aligned was: - Non-EL Property editor, cannot resize horizontally - EL Property editor, resize renders too slowly - Is empty check box positioning is off - window resize event needs to resize any visible properties tables - Property table heights are too short. > Properties Tables > - > > Key: NIFI-2027 > URL: https://issues.apache.org/jira/browse/NIFI-2027 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Scott Aslan > Fix For: 1.0.0 > > > - Non-EL Property editor, cannot resize horizontally > - EL Property editor, resize renders too slowly > - Is empty check box positioning is off > - window resize event needs to resize any visible properties tables > - Property table heights are too short > - GoTo icon is right aligned -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2027) Properties Tables
[ https://issues.apache.org/jira/browse/NIFI-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2027: -- Description: - Non-EL Property editor, cannot resize horizontally - EL Property editor, resize renders too slowly - Is empty check box positioning is off - window resize event needs to resize any visible properties tables - Property table heights are too short. was: - Non-EL Property editor, cannot resize horizontally - EL Property editor, resize renders too slowly - Is empty check box positioning is off - window resize event needs to resize any visible properties tables > Properties Tables > - > > Key: NIFI-2027 > URL: https://issues.apache.org/jira/browse/NIFI-2027 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Scott Aslan > Fix For: 1.0.0 > > > - Non-EL Property editor, cannot resize horizontally > - EL Property editor, resize renders too slowly > - Is empty check box positioning is off > - window resize event needs to resize any visible properties tables > - Property table heights are too short. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2075) Provenance Issues
Matt Gilman created NIFI-2075: - Summary: Provenance Issues Key: NIFI-2075 URL: https://issues.apache.org/jira/browse/NIFI-2075 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Matt Gilman Fix For: 1.0.0 - Styles in provenance page are not correct when in the shell. - Loading dialog does not close when in the shell. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1946) UI - Palette's
[ https://issues.apache.org/jira/browse/NIFI-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1946: -- Attachment: (was: 0001-NIFI-1946.patch) > UI - Palette's > -- > > Key: NIFI-1946 > URL: https://issues.apache.org/jira/browse/NIFI-1946 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > Attachments: 0001-NIFI-1946.patch > > > - Expand by default > - Align palette handles in the top left of the canvas -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1946) UI - Palette's
[ https://issues.apache.org/jira/browse/NIFI-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1946: -- Attachment: 0001-NIFI-1946.patch Updating patch to address issue with showing a Connection in the selection context. > UI - Palette's > -- > > Key: NIFI-1946 > URL: https://issues.apache.org/jira/browse/NIFI-1946 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > Attachments: 0001-NIFI-1946.patch > > > - Expand by default > - Align palette handles in the top left of the canvas -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1882) Templates - Ensure Controller Services are scoped by Process Group
[ https://issues.apache.org/jira/browse/NIFI-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1882: -- Assignee: Mark Payne (was: Matt Gilman) > Templates - Ensure Controller Services are scoped by Process Group > -- > > Key: NIFI-1882 > URL: https://issues.apache.org/jira/browse/NIFI-1882 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Mark Payne > Fix For: 1.0.0 > > > When a component that references a Controller Service is included in a > Template, that Controller Service is included at the top level of that > Template. This should be the case if the Controller Service is outside of the > top level Process Group being templated. However, is a descendant component > references a Controller Service that service should be stored in the > correctly scoped Process Group. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-1882) Templates - Ensure Controller Services are scoped by Process Group
[ https://issues.apache.org/jira/browse/NIFI-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-1882: - Assignee: Matt Gilman (was: Mark Payne) > Templates - Ensure Controller Services are scoped by Process Group > -- > > Key: NIFI-1882 > URL: https://issues.apache.org/jira/browse/NIFI-1882 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > When a component that references a Controller Service is included in a > Template, that Controller Service is included at the top level of that > Template. This should be the case if the Controller Service is outside of the > top level Process Group being templated. However, is a descendant component > references a Controller Service that service should be stored in the > correctly scoped Process Group. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1946) UI - Palette's
[ https://issues.apache.org/jira/browse/NIFI-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1946: -- Attachment: 0001-NIFI-1946.patch > UI - Palette's > -- > > Key: NIFI-1946 > URL: https://issues.apache.org/jira/browse/NIFI-1946 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > Attachments: 0001-NIFI-1946.patch > > > - Expand by default > - Align palette handles in the top left of the canvas -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2064) Cluster - Unable to merge Process Group status
[
https://issues.apache.org/jira/browse/NIFI-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman resolved NIFI-2064.
---
Resolution: Fixed
Assignee: Matt Gilman
Resovled in this commit [1].
[1]
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=8b27ed905d076b7571736995ef0d2ca48132b156
> Cluster - Unable to merge Process Group status
> --
>
> Key: NIFI-2064
> URL: https://issues.apache.org/jira/browse/NIFI-2064
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.0.0
>
>
> Unable to open Summary while clustered.
> {noformat}
> java.lang.NullPointerException: null
> at
> org.apache.nifi.cluster.coordination.http.endpoints.GroupStatusEndpointMerger.mergeResponses(GroupStatusEndpointMerger.java:76)
> ~[nifi-framework-cluster-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.cluster.coordination.http.endpoints.GroupStatusEndpointMerger.mergeResponses(GroupStatusEndpointMerger.java:35)
> ~[nifi-framework-cluster-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.cluster.coordination.http.endpoints.AbstractNodeStatusEndpoint.mergeResponses(AbstractNodeStatusEndpoint.java:41)
> ~[nifi-framework-cluster-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> at
> org.apache.nifi.cluster.coordination.http.endpoints.AbstractSingleDTOEndpoint.merge(AbstractSingleDTOEndpoint.java:48)
> ~[nifi-framework-cluster-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (NIFI-2064) Cluster - Unable to merge Process Group status
Matt Gilman created NIFI-2064:
-
Summary: Cluster - Unable to merge Process Group status
Key: NIFI-2064
URL: https://issues.apache.org/jira/browse/NIFI-2064
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Reporter: Matt Gilman
Fix For: 1.0.0
Unable to open Summary while clustered.
{noformat}
java.lang.NullPointerException: null
at
org.apache.nifi.cluster.coordination.http.endpoints.GroupStatusEndpointMerger.mergeResponses(GroupStatusEndpointMerger.java:76)
~[nifi-framework-cluster-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.cluster.coordination.http.endpoints.GroupStatusEndpointMerger.mergeResponses(GroupStatusEndpointMerger.java:35)
~[nifi-framework-cluster-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.cluster.coordination.http.endpoints.AbstractNodeStatusEndpoint.mergeResponses(AbstractNodeStatusEndpoint.java:41)
~[nifi-framework-cluster-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
at
org.apache.nifi.cluster.coordination.http.endpoints.AbstractSingleDTOEndpoint.merge(AbstractSingleDTOEndpoint.java:48)
~[nifi-framework-cluster-1.0.0-SNAPSHOT.jar:1.0.0-SNAPSHOT]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (NIFI-1882) Templates - Ensure Controller Services are scoped by Process Group
[ https://issues.apache.org/jira/browse/NIFI-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-1882. --- Resolution: Fixed > Templates - Ensure Controller Services are scoped by Process Group > -- > > Key: NIFI-1882 > URL: https://issues.apache.org/jira/browse/NIFI-1882 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Mark Payne > Fix For: 1.0.0 > > > When a component that references a Controller Service is included in a > Template, that Controller Service is included at the top level of that > Template. This should be the case if the Controller Service is outside of the > top level Process Group being templated. However, is a descendant component > references a Controller Service that service should be stored in the > correctly scoped Process Group. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1882) Templates - Ensure Controller Services are scoped by Process Group
[ https://issues.apache.org/jira/browse/NIFI-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1882: -- Assignee: Mark Payne > Templates - Ensure Controller Services are scoped by Process Group > -- > > Key: NIFI-1882 > URL: https://issues.apache.org/jira/browse/NIFI-1882 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Mark Payne > Fix For: 1.0.0 > > > When a component that references a Controller Service is included in a > Template, that Controller Service is included at the top level of that > Template. This should be the case if the Controller Service is outside of the > top level Process Group being templated. However, is a descendant component > references a Controller Service that service should be stored in the > correctly scoped Process Group. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2024) New processor displayed as white rectangle on a white background in birdseye
[ https://issues.apache.org/jira/browse/NIFI-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2024. --- Resolution: Duplicate > New processor displayed as white rectangle on a white background in birdseye > > > Key: NIFI-2024 > URL: https://issues.apache.org/jira/browse/NIFI-2024 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Scott Aslan > Fix For: 1.0.0 > > Attachments: screenshot-1.png > > > When adding a new processor to the canvas the birdseye view displays the > processor as a white rectangle. Since the background is white it is difficult > to see it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1946) UI - Palette's
[ https://issues.apache.org/jira/browse/NIFI-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1946: -- Issue Type: Sub-task (was: Improvement) Parent: NIFI-2010 > UI - Palette's > -- > > Key: NIFI-1946 > URL: https://issues.apache.org/jira/browse/NIFI-1946 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > - Expand by default > - Align palette handles in the top left of the canvas -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2059) Secure cluster request replication
Matt Gilman created NIFI-2059: - Summary: Secure cluster request replication Key: NIFI-2059 URL: https://issues.apache.org/jira/browse/NIFI-2059 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Matt Gilman Priority: Blocker Fix For: 1.0.0 I attempted to stand up a secure cluster and was having issues with request replication. It appears that with the current approach every node will need to authorize every other node as a proxy and we need to ensure those requests are being replicated on behalf of the end user. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2012) Reposition Navigate and Operate palette
[ https://issues.apache.org/jira/browse/NIFI-2012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2012. --- Resolution: Duplicate Fix Version/s: 1.0.0 > Reposition Navigate and Operate palette > --- > > Key: NIFI-2012 > URL: https://issues.apache.org/jira/browse/NIFI-2012 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Rob Moran >Priority: Minor > Fix For: 1.0.0 > > > Move these up to top left of the canvas (20px below flow status) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2011) Set Navigate and Operate palette to be open by default
[ https://issues.apache.org/jira/browse/NIFI-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2011. --- Resolution: Duplicate Fix Version/s: 1.0.0 > Set Navigate and Operate palette to be open by default > -- > > Key: NIFI-2011 > URL: https://issues.apache.org/jira/browse/NIFI-2011 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Affects Versions: 1.0.0 >Reporter: Rob Moran >Priority: Critical > Fix For: 1.0.0 > > > This needs to done so users do not have to hunt for these controls when they > first see the new design -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2054) User "has-pending-accounts"
[ https://issues.apache.org/jira/browse/NIFI-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2054. --- Resolution: Not A Problem This capability is OBE. If/when we introduce account requests we can reopen the issue. > User "has-pending-accounts" > --- > > Key: NIFI-2054 > URL: https://issues.apache.org/jira/browse/NIFI-2054 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Scott Aslan > Fix For: 1.0.0 > > > update UX for User "has-pending-accounts" -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Deleted] (NIFI-1964) Persist flow.xml.gz on start-up so root group id is persisted
[ https://issues.apache.org/jira/browse/NIFI-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman deleted NIFI-1964: -- > Persist flow.xml.gz on start-up so root group id is persisted > - > > Key: NIFI-1964 > URL: https://issues.apache.org/jira/browse/NIFI-1964 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Bryan Bende >Priority: Minor > > Currently the flow.xml.gz is only persisted after someone accesses the UI and > takes an action like adding a processor or component. This means that if you > keep restarting NiFi without touching the UI, it will generate a different > root group id each time. > For the authorization refactoring we need to be able to access the root group > id on start up and know that it is going to be consistent regardless of > whether the UI has been accessed. We should persist the initial flow.xml.gz > after the root group id is generated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-2033) Allow Controller Services to be scoped at the Controller Level
[ https://issues.apache.org/jira/browse/NIFI-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-2033. --- Resolution: Fixed > Allow Controller Services to be scoped at the Controller Level > -- > > Key: NIFI-2033 > URL: https://issues.apache.org/jira/browse/NIFI-2033 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework >Affects Versions: 1.0.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.0.0 > > > Currently, Controller Services can be scoped to any Process Group. However, > Reporting Tasks should not be able to reference the services that are > assigned to a process group. We need to allow Controller Services to be > scoped at the Controller Level and allow them to be referenced only by > Reporting Tasks and other Controller Services that are scoped at the > Controller level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2033) Allow Controller Services to be scoped at the Controller Level
[ https://issues.apache.org/jira/browse/NIFI-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2033: -- Assignee: Mark Payne > Allow Controller Services to be scoped at the Controller Level > -- > > Key: NIFI-2033 > URL: https://issues.apache.org/jira/browse/NIFI-2033 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework >Affects Versions: 1.0.0 >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.0.0 > > > Currently, Controller Services can be scoped to any Process Group. However, > Reporting Tasks should not be able to reference the services that are > assigned to a process group. We need to allow Controller Services to be > scoped at the Controller Level and allow them to be referenced only by > Reporting Tasks and other Controller Services that are scoped at the > Controller level. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-2044) Require revision for component creation
[ https://issues.apache.org/jira/browse/NIFI-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-2044: -- Description: - When creating a component, require the revision to be specified to ensure we're using the appropriate client id. - Require component exists for PUT requests. > Require revision for component creation > --- > > Key: NIFI-2044 > URL: https://issues.apache.org/jira/browse/NIFI-2044 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Core UI >Reporter: Matt Gilman > Fix For: 1.0.0 > > > - When creating a component, require the revision to be specified to ensure > we're using the appropriate client id. > - Require component exists for PUT requests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2044) Require revision for component creation
Matt Gilman created NIFI-2044: - Summary: Require revision for component creation Key: NIFI-2044 URL: https://issues.apache.org/jira/browse/NIFI-2044 Project: Apache NiFi Issue Type: Sub-task Components: Core Framework, Core UI Reporter: Matt Gilman Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2043) UI - propertytable always uses root group id
Matt Gilman created NIFI-2043: - Summary: UI - propertytable always uses root group id Key: NIFI-2043 URL: https://issues.apache.org/jira/browse/NIFI-2043 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Fix For: 1.0.0 When the property table is initialized it is configured with the current group id. However, this value is never updated based on the current group when a component is a descendant group is configured. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2041) Unable to refresh ControllerServices by ProcessGroup
Matt Gilman created NIFI-2041: - Summary: Unable to refresh ControllerServices by ProcessGroup Key: NIFI-2041 URL: https://issues.apache.org/jira/browse/NIFI-2041 Project: Apache NiFi Issue Type: Bug Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-1941) Templates - Child Groups
[ https://issues.apache.org/jira/browse/NIFI-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-1941: - Assignee: Matt Gilman > Templates - Child Groups > > > Key: NIFI-1941 > URL: https://issues.apache.org/jira/browse/NIFI-1941 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Blocker > Fix For: 1.0.0 > > > Contents of child groups do not appear to be included in new Templates. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1871) Remote Process Group Port revision and authorization
[ https://issues.apache.org/jira/browse/NIFI-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332332#comment-15332332 ] Matt Gilman commented on NIFI-1871: --- Addressed as part of NIFI-1781. > Remote Process Group Port revision and authorization > > > Key: NIFI-1871 > URL: https://issues.apache.org/jira/browse/NIFI-1871 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Core UI >Reporter: Matt Gilman > Fix For: 1.0.0 > > > Remote Proces Group Ports need to support their own revision and > authorization(?) checking. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-1871) Remote Process Group Port revision and authorization
[ https://issues.apache.org/jira/browse/NIFI-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-1871. --- Resolution: Fixed Assignee: Matt Gilman > Remote Process Group Port revision and authorization > > > Key: NIFI-1871 > URL: https://issues.apache.org/jira/browse/NIFI-1871 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > Remote Proces Group Ports need to support their own revision and > authorization(?) checking. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2018) Update icons used in Context Menu
Matt Gilman created NIFI-2018: - Summary: Update icons used in Context Menu Key: NIFI-2018 URL: https://issues.apache.org/jira/browse/NIFI-2018 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Priority: Minor Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2019) Port status icon connected to a remote port is colored differently
Matt Gilman created NIFI-2019: - Summary: Port status icon connected to a remote port is colored differently Key: NIFI-2019 URL: https://issues.apache.org/jira/browse/NIFI-2019 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Priority: Minor Fix For: 1.0.0 Stopped icon when connected to a port in a Process Group is the normal color. Stopped icon when connected to a port in a Remote Process Group is the warm color. These should be consistent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2017) Root Group Port Transmission Icon is inaccurate
Matt Gilman created NIFI-2017: - Summary: Root Group Port Transmission Icon is inaccurate Key: NIFI-2017 URL: https://issues.apache.org/jira/browse/NIFI-2017 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Priority: Minor Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2007) Restore bulletin functionality
Matt Gilman created NIFI-2007: - Summary: Restore bulletin functionality Key: NIFI-2007 URL: https://issues.apache.org/jira/browse/NIFI-2007 Project: Apache NiFi Issue Type: Bug Components: Core Framework, Core UI Reporter: Matt Gilman Assignee: Matt Gilman Priority: Blocker Fix For: 1.0.0 Bulletin functionality broke when introducing zero master clustering. This JIRA is to restore that capability. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-2003) User Identity Normalization
Matt Gilman created NIFI-2003:
-
Summary: User Identity Normalization
Key: NIFI-2003
URL: https://issues.apache.org/jira/browse/NIFI-2003
Project: Apache NiFi
Issue Type: Sub-task
Components: Core Framework
Reporter: Matt Gilman
Fix For: 1.0.0
NiFi allows for a number of different authentication mechanisms. Once the user
has authenticated he/she is identified by their identity. This is a String that
is returned by the authentication mechanism. For certificate or LDAP based
authentication this is a DN. For Kerberos it is the user principal. If the same
user authenticates through different mechanisms, they may have different
identities. In 0.x this was annoying but not a big deal as it was just a matter
of (re)assigning the user role. However, in 1.x this is unacceptable given the
nature of fine grain authorization and the number of access policies that must
be duplicated.
Because we’ve delegated user authorization and the underlying implementation
can choose to authenticate however they want, we cannot rely on our internal
User/Group/Policy model to enforce any normalization.
After discussions with Andy, Joe, and Bryan, I think we have a proposal that
will provide the flexibility needed without requiring continued maintenance by
an Administrator. Additionally, it shouldn’t require too many additional
development cycles.
The basic idea is to add configurable mappings that will run after the user
identity determined but before any authorizations. These mappings are
purposefully decoupled from the authentication mechanisms to reduce duplicative
configurations and support a more flexible solution. These mappings could be
configured in nifi.properties as follows. Here, the last segment of the
property name is an identifier used to associate the pattern with the
replacement value.
{noformat}
nifi.security.identity.mapping.pattern.dn=^cn=(.*?),dc=(.*?),dc=(.*?)$
nifi.security.identity.mapping.value.dn=$1@$2.$3
nifi.security.identity.mapping.pattern.kerb=^(.*?)/instance@(.*?)$
nifi.security.identity.mapping.value.kerb=$1@$2
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (NIFI-1883) Controller Service referencing components
[ https://issues.apache.org/jira/browse/NIFI-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-1883. --- Resolution: Fixed > Controller Service referencing components > - > > Key: NIFI-1883 > URL: https://issues.apache.org/jira/browse/NIFI-1883 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > Controller Service referencing components are not restored at start up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-1883) Controller Service referencing components
[ https://issues.apache.org/jira/browse/NIFI-1883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-1883: - Assignee: Matt Gilman > Controller Service referencing components > - > > Key: NIFI-1883 > URL: https://issues.apache.org/jira/browse/NIFI-1883 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > Controller Service referencing components are not restored at start up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1967) nifi.properties conversion for 1.0.0
[ https://issues.apache.org/jira/browse/NIFI-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314343#comment-15314343 ] Matt Gilman commented on NIFI-1967: --- Fair points. Just want to suggest that we do something. A migration guide would be perfectly suitable. > nifi.properties conversion for 1.0.0 > > > Key: NIFI-1967 > URL: https://issues.apache.org/jira/browse/NIFI-1967 > Project: Apache NiFi > Issue Type: Improvement > Components: Configuration >Reporter: Matt Gilman >Priority: Minor > Fix For: 1.0.0 > > > With the properties changing it would be nice to offer an automated way of > converting an existing nifi.properties to the 1.0.0 version. Specifically, > the clustering properties have changed enough to warrant scripting this for > users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1967) nifi.properties conversion for 1.0.0
Matt Gilman created NIFI-1967: - Summary: nifi.properties conversion for 1.0.0 Key: NIFI-1967 URL: https://issues.apache.org/jira/browse/NIFI-1967 Project: Apache NiFi Issue Type: Improvement Components: Configuration Reporter: Matt Gilman Priority: Minor Fix For: 1.0.0 With the properties changing it would be nice to offer an automated way of converting an existing nifi.properties to the 1.0.0 version. Specifically, the clustering properties have changed enough to warrant scripting this for users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1966) Cluster - Coordinator Determination Issues
Matt Gilman created NIFI-1966: - Summary: Cluster - Coordinator Determination Issues Key: NIFI-1966 URL: https://issues.apache.org/jira/browse/NIFI-1966 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Matt Gilman Priority: Blocker Fix For: 1.0.0 During startup a coordinator is selected at random to act as the manager of data flow and distributing it to other nodes. This works fine unless that selected coordinator happens to have a uninheritable data flow. When this occurs, the other nodes either are - Able to connect to Coordinator and then unable to join due to an uninheritable flow exception due to being presented with a bad data flow. In this case, the node shut down. - Unable to connect to the Coordinator due to lack of quorem and never present with the bad data flow. In this case, the node ran its local flow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1963) Cluster - Flow inheritability
Matt Gilman created NIFI-1963: - Summary: Cluster - Flow inheritability Key: NIFI-1963 URL: https://issues.apache.org/jira/browse/NIFI-1963 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Matt Gilman Fix For: 1.0.0 I disconnected a node and changed the penalty duration. The attempted to reconnect the node. The node joined successfully with an inconsistent penalty duration. Need to reconsider which fields need to belong in the flow fingerprint to ensure consistent configuration throughout the cluster. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1961) Test Resource - nifi.properties
Matt Gilman created NIFI-1961: - Summary: Test Resource - nifi.properties Key: NIFI-1961 URL: https://issues.apache.org/jira/browse/NIFI-1961 Project: Apache NiFi Issue Type: Task Components: Core Framework Reporter: Matt Gilman Priority: Trivial Fix For: 1.0.0 Many tests reference a copy of nifi.properties. These copies have become increasingly stale with as the application has evolved. With the changes in 1.x we should at the very least update the copies or better yet, update the tests to mock out the necessary configuration to avoid the copies all together. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1960) Documentation
Matt Gilman created NIFI-1960: - Summary: Documentation Key: NIFI-1960 URL: https://issues.apache.org/jira/browse/NIFI-1960 Project: Apache NiFi Issue Type: Task Components: Documentation & Website Reporter: Matt Gilman Priority: Blocker Fix For: 1.0.0 Several parts of the application are fundamentally different in 1.x. Specifically, documentation around clustering and authorization need to be completely revisited. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-1928) UI - Remove registration process
[ https://issues.apache.org/jira/browse/NIFI-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-1928. --- Resolution: Fixed > UI - Remove registration process > > > Key: NIFI-1928 > URL: https://issues.apache.org/jira/browse/NIFI-1928 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > With the updated user authorization model, users will no longer be able to > request an account. Instead, users are authorized through the configured > Authorizer implementation (it's pluggable). Consequently, we can remove all > the account registration forms from the UI and OBE REST endpoints. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-1948) Templates created should include template encoding version
[ https://issues.apache.org/jira/browse/NIFI-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-1948. --- Resolution: Fixed > Templates created should include template encoding version > -- > > Key: NIFI-1948 > URL: https://issues.apache.org/jira/browse/NIFI-1948 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework >Affects Versions: 1.0.0 >Reporter: Jeff Storck >Assignee: Jeff Storck > Fix For: 1.0.0 > > > Templates created, starting with version Apache NiFi 1.0.0, should include > the template encoding version. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1951) Custom UIs
[ https://issues.apache.org/jira/browse/NIFI-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1951: -- Description: - Remove deprecated NiFiWebContext and related classes - Ensure appropriate access for calls into NiFiWebConfigurationContext > Custom UIs > -- > > Key: NIFI-1951 > URL: https://issues.apache.org/jira/browse/NIFI-1951 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > - Remove deprecated NiFiWebContext and related classes > - Ensure appropriate access for calls into NiFiWebConfigurationContext -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1951) Custom UIs
[ https://issues.apache.org/jira/browse/NIFI-1951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1951: -- Summary: Custom UIs (was: Remove Deprecated NiFiWebContext and related Classes) > Custom UIs > -- > > Key: NIFI-1951 > URL: https://issues.apache.org/jira/browse/NIFI-1951 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1951) Remove Deprecated NiFiWebContext and related Classes
Matt Gilman created NIFI-1951: - Summary: Remove Deprecated NiFiWebContext and related Classes Key: NIFI-1951 URL: https://issues.apache.org/jira/browse/NIFI-1951 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Matt Gilman Assignee: Matt Gilman Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1850) JSON-to-JSON Schema Converter Editor
[ https://issues.apache.org/jira/browse/NIFI-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1850: -- Assignee: Yolanda M. Davis > JSON-to-JSON Schema Converter Editor > > > Key: NIFI-1850 > URL: https://issues.apache.org/jira/browse/NIFI-1850 > Project: Apache NiFi > Issue Type: New Feature > Components: Core UI >Reporter: Yolanda M. Davis >Assignee: Yolanda M. Davis >Priority: Minor > Fix For: 0.7.0 > > > With NIFI-361 implemented, users can embed a JOLT spec into the TransformJSON > processor. However, building the spec is not intuitive enough without the > ability to obtain real time feedback on spec syntax and preview output data. > Would like to have a specification editor and transform preview view added > to the processor configuration screen to allow users to immediately see the > impact on the output JSON data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (NIFI-1850) JSON-to-JSON Schema Converter Editor
[ https://issues.apache.org/jira/browse/NIFI-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-1850. --- Resolution: Fixed Fix Version/s: (was: 1.0.0) > JSON-to-JSON Schema Converter Editor > > > Key: NIFI-1850 > URL: https://issues.apache.org/jira/browse/NIFI-1850 > Project: Apache NiFi > Issue Type: New Feature > Components: Core UI >Reporter: Yolanda M. Davis >Assignee: Yolanda M. Davis >Priority: Minor > Fix For: 0.7.0 > > > With NIFI-361 implemented, users can embed a JOLT spec into the TransformJSON > processor. However, building the spec is not intuitive enough without the > ability to obtain real time feedback on spec syntax and preview output data. > Would like to have a specification editor and transform preview view added > to the processor configuration screen to allow users to immediately see the > impact on the output JSON data. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1950) Convert 0.x site-to-site access policies when possible
Matt Gilman created NIFI-1950: - Summary: Convert 0.x site-to-site access policies when possible Key: NIFI-1950 URL: https://issues.apache.org/jira/browse/NIFI-1950 Project: Apache NiFi Issue Type: Sub-task Components: Core Framework Reporter: Matt Gilman Priority: Blocker Fix For: 1.0.0 In the 0.x baseline access a Remote Port is configurable. These authorizations are stored in the flow.xml. In the 1.0.0 baseline these decisions will be made by a configurable authorizer. When possible, these access policies need to be converted to the authorizer upon starting with a legacy flow. Note: This won't be possible when the authorizer is externally managed. When this is the case, we'll need to document that the access policies will need to be manually restored using the external tool the authorizer supports. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1946) UI - Palette's
[ https://issues.apache.org/jira/browse/NIFI-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1946: -- Fix Version/s: 1.0.0 > UI - Palette's > -- > > Key: NIFI-1946 > URL: https://issues.apache.org/jira/browse/NIFI-1946 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > - Expand by default > - Align palette handles in the top left of the canvas -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1946) UI - Palette's
[ https://issues.apache.org/jira/browse/NIFI-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1946: -- Description: - Expand by default - Align palette handles in the top left of the canvas was: - Expand by default - Top aling palette handles in the top left of the > UI - Palette's > -- > > Key: NIFI-1946 > URL: https://issues.apache.org/jira/browse/NIFI-1946 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > > - Expand by default > - Align palette handles in the top left of the canvas -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1946) UI - Palette's
[ https://issues.apache.org/jira/browse/NIFI-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1946: -- Description: - Expand by default - Top aling palette handles in the top left of the > UI - Palette's > -- > > Key: NIFI-1946 > URL: https://issues.apache.org/jira/browse/NIFI-1946 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > > - Expand by default > - Top aling palette handles in the top left of the -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1946) UI - Palette's
[ https://issues.apache.org/jira/browse/NIFI-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1946: -- Summary: UI - Palette's (was: UI - Expand Palette's by default) > UI - Palette's > -- > > Key: NIFI-1946 > URL: https://issues.apache.org/jira/browse/NIFI-1946 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1946) UI - Expand Palette's by default
Matt Gilman created NIFI-1946: - Summary: UI - Expand Palette's by default Key: NIFI-1946 URL: https://issues.apache.org/jira/browse/NIFI-1946 Project: Apache NiFi Issue Type: Improvement Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1944) Use GzipHandler instead of GzipFilter
Matt Gilman created NIFI-1944:
-
Summary: Use GzipHandler instead of GzipFilter
Key: NIFI-1944
URL: https://issues.apache.org/jira/browse/NIFI-1944
Project: Apache NiFi
Issue Type: Improvement
Components: Core Framework
Reporter: Matt Gilman
Priority: Minor
Fix For: 1.0.0
>From the app log...
{noformat}
2016-05-31 12:32:31,507 WARN [main] o.eclipse.jetty.util.DeprecationWarning
Using @Deprecated Class org.eclipse.jetty.servlets.GzipFilter
2016-05-31 12:32:31,510 WARN [main] org.eclipse.jetty.servlets.GzipFilter
GzipFilter is deprecated. Use GzipHandler
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (NIFI-1882) Templates - Ensure Controller Services are scoped by Process Group
[ https://issues.apache.org/jira/browse/NIFI-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1882: -- Summary: Templates - Ensure Controller Services are scoped by Process Group (was: Template - Ensure Controller Services are scoped by Process Group) > Templates - Ensure Controller Services are scoped by Process Group > -- > > Key: NIFI-1882 > URL: https://issues.apache.org/jira/browse/NIFI-1882 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Reporter: Matt Gilman > Fix For: 1.0.0 > > > When a component that references a Controller Service is included in a > Template, that Controller Service is included at the top level of that > Template. This should be the case if the Controller Service is outside of the > top level Process Group being templated. However, is a descendant component > references a Controller Service that service should be stored in the > correctly scoped Process Group. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1941) Templates - Child Groups
Matt Gilman created NIFI-1941: - Summary: Templates - Child Groups Key: NIFI-1941 URL: https://issues.apache.org/jira/browse/NIFI-1941 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Matt Gilman Priority: Blocker Fix For: 1.0.0 Contents of child groups do not appear to be included in new Templates. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1265) Precompiling message-page.jsp causes runtime error in CentOS 6.7 and Fedora 23
[
https://issues.apache.org/jira/browse/NIFI-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-1265:
--
Fix Version/s: (was: 0.7.0)
1.0.0
> Precompiling message-page.jsp causes runtime error in CentOS 6.7 and Fedora 23
> --
>
> Key: NIFI-1265
> URL: https://issues.apache.org/jira/browse/NIFI-1265
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 1.0.0
>
> Attachments: jetty.447816.patch
>
>
> During start up it appears that when message-page.jsp is precompiled and run
> in CentOS 6.7 or Fedora 23 the following method in ServletHolder (Jetty)
> fails with:
> {noformat}
> 2015-12-07 10:01:26,557 WARN [main] org.apache.nifi.web.server.JettyServer
> Failed to start web server... shutting down.
> java.lang.IllegalArgumentException: Comparison method violates its general
> contract!
> at java.util.ComparableTimSort.mergeHi(ComparableTimSort.java:866)
> ~[na:1.8.0_65]
> at java.util.ComparableTimSort.mergeAt(ComparableTimSort.java:483)
> ~[na:1.8.0_65]
> at
> java.util.ComparableTimSort.mergeForceCollapse(ComparableTimSort.java:422)
> ~[na:1.8.0_65]
> at java.util.ComparableTimSort.sort(ComparableTimSort.java:222)
> ~[na:1.8.0_65]
> at java.util.Arrays.sort(Arrays.java:1246) ~[na:1.8.0_65]
> at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:865)
> ~[jetty-servlet-9.2.11.v20150529.jar:9.2.11.v20150529]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298)
> ~[jetty-servlet-9.2.11.v20150529.jar:9.2.11.v20150529]
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> ~[jetty-webapp-9.2.11.v20150529.jar:9.2.11.v20150529]
> {noformat}
> {code}
> @Override
> public int compareTo(ServletHolder sh)
> {
> if (sh==this)
> return 0;
> if (sh._initOrder<_initOrder)
> return 1;
> if (sh._initOrder>_initOrder)
> return -1;
> int c=(_className!=null &&
> sh._className!=null)?_className.compareTo(sh._className):0;
> if (c==0)
> c=_name.compareTo(sh._name);
> return c;
> }
> {code}
> After a quick glance it may be that this method is not transitive when
> falling back to comparing by className and name. From the Java API
> {noformat}
> The implementor must also ensure that the relation is transitive:
> ((compare(x, y)>0) && (compare(y, z)>0)) implies compare(x, z)>0.
> {noformat}
> This could fail with the following scenario:
> {noformat}
> x._initOrder = -1
> x._className = null
> x._name = Login
> y._initOrder = -1
> y._className = org.apache.nifi.web.jsp.WEB_002dINF.pages.message_002dpage_jsp
> y._name = org.apache.nifi.web.jsp.WEB_002dINF.pages.message_002dpage_jsp
> z._initOrder = -1
> z._className = org.apache.nifi.web.servlet.DownloadSvg
> z._name = DownloadSvg
> {noformat}
> Unfortunately, I am unable to replicate the exception. However, my
> observation from debugging show that when JSPs are precompiled the _className
> and _name are the same (like y above). When a Servlet is referenced in the
> web.xml it's name is overridden (like z above). And when a JSP is referenced
> in the web.xml the _className is null and the _name is set to the name from
> the web.xml (like x above).
> In the scenario outlined: X < Y and Y < Z but Z < X. When running locally I
> did not see the exception mentioned above but the resulting sort order was
> not correct as it ultimately depended on which elements were compared to each
> other.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-1265) Precompiling message-page.jsp causes runtime error in CentOS 6.7 and Fedora 23
[
https://issues.apache.org/jira/browse/NIFI-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304510#comment-15304510
]
Matt Gilman commented on NIFI-1265:
---
Looks like Jetty 9.3.x requires Java 8 [1]. Without Jetty rolling that patch
back to a 9.2.x release it does not appear that we'll be able to upgrade on our
0.x baseline.
[1] http://www.eclipse.org/jetty/documentation/current/what-jetty-version.html
> Precompiling message-page.jsp causes runtime error in CentOS 6.7 and Fedora 23
> --
>
> Key: NIFI-1265
> URL: https://issues.apache.org/jira/browse/NIFI-1265
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 0.7.0
>
> Attachments: jetty.447816.patch
>
>
> During start up it appears that when message-page.jsp is precompiled and run
> in CentOS 6.7 or Fedora 23 the following method in ServletHolder (Jetty)
> fails with:
> {noformat}
> 2015-12-07 10:01:26,557 WARN [main] org.apache.nifi.web.server.JettyServer
> Failed to start web server... shutting down.
> java.lang.IllegalArgumentException: Comparison method violates its general
> contract!
> at java.util.ComparableTimSort.mergeHi(ComparableTimSort.java:866)
> ~[na:1.8.0_65]
> at java.util.ComparableTimSort.mergeAt(ComparableTimSort.java:483)
> ~[na:1.8.0_65]
> at
> java.util.ComparableTimSort.mergeForceCollapse(ComparableTimSort.java:422)
> ~[na:1.8.0_65]
> at java.util.ComparableTimSort.sort(ComparableTimSort.java:222)
> ~[na:1.8.0_65]
> at java.util.Arrays.sort(Arrays.java:1246) ~[na:1.8.0_65]
> at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:865)
> ~[jetty-servlet-9.2.11.v20150529.jar:9.2.11.v20150529]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298)
> ~[jetty-servlet-9.2.11.v20150529.jar:9.2.11.v20150529]
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> ~[jetty-webapp-9.2.11.v20150529.jar:9.2.11.v20150529]
> {noformat}
> {code}
> @Override
> public int compareTo(ServletHolder sh)
> {
> if (sh==this)
> return 0;
> if (sh._initOrder<_initOrder)
> return 1;
> if (sh._initOrder>_initOrder)
> return -1;
> int c=(_className!=null &&
> sh._className!=null)?_className.compareTo(sh._className):0;
> if (c==0)
> c=_name.compareTo(sh._name);
> return c;
> }
> {code}
> After a quick glance it may be that this method is not transitive when
> falling back to comparing by className and name. From the Java API
> {noformat}
> The implementor must also ensure that the relation is transitive:
> ((compare(x, y)>0) && (compare(y, z)>0)) implies compare(x, z)>0.
> {noformat}
> This could fail with the following scenario:
> {noformat}
> x._initOrder = -1
> x._className = null
> x._name = Login
> y._initOrder = -1
> y._className = org.apache.nifi.web.jsp.WEB_002dINF.pages.message_002dpage_jsp
> y._name = org.apache.nifi.web.jsp.WEB_002dINF.pages.message_002dpage_jsp
> z._initOrder = -1
> z._className = org.apache.nifi.web.servlet.DownloadSvg
> z._name = DownloadSvg
> {noformat}
> Unfortunately, I am unable to replicate the exception. However, my
> observation from debugging show that when JSPs are precompiled the _className
> and _name are the same (like y above). When a Servlet is referenced in the
> web.xml it's name is overridden (like z above). And when a JSP is referenced
> in the web.xml the _className is null and the _name is set to the name from
> the web.xml (like x above).
> In the scenario outlined: X < Y and Y < Z but Z < X. When running locally I
> did not see the exception mentioned above but the resulting sort order was
> not correct as it ultimately depended on which elements were compared to each
> other.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (NIFI-1265) Precompiling message-page.jsp causes runtime error in CentOS 6.7 and Fedora 23
[
https://issues.apache.org/jira/browse/NIFI-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman reassigned NIFI-1265:
-
Assignee: Matt Gilman
> Precompiling message-page.jsp causes runtime error in CentOS 6.7 and Fedora 23
> --
>
> Key: NIFI-1265
> URL: https://issues.apache.org/jira/browse/NIFI-1265
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Minor
> Fix For: 0.7.0
>
> Attachments: jetty.447816.patch
>
>
> During start up it appears that when message-page.jsp is precompiled and run
> in CentOS 6.7 or Fedora 23 the following method in ServletHolder (Jetty)
> fails with:
> {noformat}
> 2015-12-07 10:01:26,557 WARN [main] org.apache.nifi.web.server.JettyServer
> Failed to start web server... shutting down.
> java.lang.IllegalArgumentException: Comparison method violates its general
> contract!
> at java.util.ComparableTimSort.mergeHi(ComparableTimSort.java:866)
> ~[na:1.8.0_65]
> at java.util.ComparableTimSort.mergeAt(ComparableTimSort.java:483)
> ~[na:1.8.0_65]
> at
> java.util.ComparableTimSort.mergeForceCollapse(ComparableTimSort.java:422)
> ~[na:1.8.0_65]
> at java.util.ComparableTimSort.sort(ComparableTimSort.java:222)
> ~[na:1.8.0_65]
> at java.util.Arrays.sort(Arrays.java:1246) ~[na:1.8.0_65]
> at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:865)
> ~[jetty-servlet-9.2.11.v20150529.jar:9.2.11.v20150529]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298)
> ~[jetty-servlet-9.2.11.v20150529.jar:9.2.11.v20150529]
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> ~[jetty-webapp-9.2.11.v20150529.jar:9.2.11.v20150529]
> {noformat}
> {code}
> @Override
> public int compareTo(ServletHolder sh)
> {
> if (sh==this)
> return 0;
> if (sh._initOrder<_initOrder)
> return 1;
> if (sh._initOrder>_initOrder)
> return -1;
> int c=(_className!=null &&
> sh._className!=null)?_className.compareTo(sh._className):0;
> if (c==0)
> c=_name.compareTo(sh._name);
> return c;
> }
> {code}
> After a quick glance it may be that this method is not transitive when
> falling back to comparing by className and name. From the Java API
> {noformat}
> The implementor must also ensure that the relation is transitive:
> ((compare(x, y)>0) && (compare(y, z)>0)) implies compare(x, z)>0.
> {noformat}
> This could fail with the following scenario:
> {noformat}
> x._initOrder = -1
> x._className = null
> x._name = Login
> y._initOrder = -1
> y._className = org.apache.nifi.web.jsp.WEB_002dINF.pages.message_002dpage_jsp
> y._name = org.apache.nifi.web.jsp.WEB_002dINF.pages.message_002dpage_jsp
> z._initOrder = -1
> z._className = org.apache.nifi.web.servlet.DownloadSvg
> z._name = DownloadSvg
> {noformat}
> Unfortunately, I am unable to replicate the exception. However, my
> observation from debugging show that when JSPs are precompiled the _className
> and _name are the same (like y above). When a Servlet is referenced in the
> web.xml it's name is overridden (like z above). And when a JSP is referenced
> in the web.xml the _className is null and the _name is set to the name from
> the web.xml (like x above).
> In the scenario outlined: X < Y and Y < Z but Z < X. When running locally I
> did not see the exception mentioned above but the resulting sort order was
> not correct as it ultimately depended on which elements were compared to each
> other.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (NIFI-1265) Precompiling message-page.jsp causes runtime error in CentOS 6.7 and Fedora 23
[
https://issues.apache.org/jira/browse/NIFI-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303386#comment-15303386
]
Matt Gilman commented on NIFI-1265:
---
I believe in the previous comment, the patch was applied to the latest stable
9.2 and rebuilt locally. I don't believe the patch is available in any released
version of 9.2.
The confirmation that it does fix the issue is great however, as I've still
never been able to replicate it. We'll get this into 0.7.0 for sure.
> Precompiling message-page.jsp causes runtime error in CentOS 6.7 and Fedora 23
> --
>
> Key: NIFI-1265
> URL: https://issues.apache.org/jira/browse/NIFI-1265
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core UI
>Reporter: Matt Gilman
>Priority: Minor
> Fix For: 0.7.0
>
> Attachments: jetty.447816.patch
>
>
> During start up it appears that when message-page.jsp is precompiled and run
> in CentOS 6.7 or Fedora 23 the following method in ServletHolder (Jetty)
> fails with:
> {noformat}
> 2015-12-07 10:01:26,557 WARN [main] org.apache.nifi.web.server.JettyServer
> Failed to start web server... shutting down.
> java.lang.IllegalArgumentException: Comparison method violates its general
> contract!
> at java.util.ComparableTimSort.mergeHi(ComparableTimSort.java:866)
> ~[na:1.8.0_65]
> at java.util.ComparableTimSort.mergeAt(ComparableTimSort.java:483)
> ~[na:1.8.0_65]
> at
> java.util.ComparableTimSort.mergeForceCollapse(ComparableTimSort.java:422)
> ~[na:1.8.0_65]
> at java.util.ComparableTimSort.sort(ComparableTimSort.java:222)
> ~[na:1.8.0_65]
> at java.util.Arrays.sort(Arrays.java:1246) ~[na:1.8.0_65]
> at
> org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:865)
> ~[jetty-servlet-9.2.11.v20150529.jar:9.2.11.v20150529]
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:298)
> ~[jetty-servlet-9.2.11.v20150529.jar:9.2.11.v20150529]
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> ~[jetty-webapp-9.2.11.v20150529.jar:9.2.11.v20150529]
> {noformat}
> {code}
> @Override
> public int compareTo(ServletHolder sh)
> {
> if (sh==this)
> return 0;
> if (sh._initOrder<_initOrder)
> return 1;
> if (sh._initOrder>_initOrder)
> return -1;
> int c=(_className!=null &&
> sh._className!=null)?_className.compareTo(sh._className):0;
> if (c==0)
> c=_name.compareTo(sh._name);
> return c;
> }
> {code}
> After a quick glance it may be that this method is not transitive when
> falling back to comparing by className and name. From the Java API
> {noformat}
> The implementor must also ensure that the relation is transitive:
> ((compare(x, y)>0) && (compare(y, z)>0)) implies compare(x, z)>0.
> {noformat}
> This could fail with the following scenario:
> {noformat}
> x._initOrder = -1
> x._className = null
> x._name = Login
> y._initOrder = -1
> y._className = org.apache.nifi.web.jsp.WEB_002dINF.pages.message_002dpage_jsp
> y._name = org.apache.nifi.web.jsp.WEB_002dINF.pages.message_002dpage_jsp
> z._initOrder = -1
> z._className = org.apache.nifi.web.servlet.DownloadSvg
> z._name = DownloadSvg
> {noformat}
> Unfortunately, I am unable to replicate the exception. However, my
> observation from debugging show that when JSPs are precompiled the _className
> and _name are the same (like y above). When a Servlet is referenced in the
> web.xml it's name is overridden (like z above). And when a JSP is referenced
> in the web.xml the _className is null and the _name is set to the name from
> the web.xml (like x above).
> In the scenario outlined: X < Y and Y < Z but Z < X. When running locally I
> did not see the exception mentioned above but the resulting sort order was
> not correct as it ultimately depended on which elements were compared to each
> other.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (NIFI-1928) UI - Remove registration process
[ https://issues.apache.org/jira/browse/NIFI-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1928: -- Description: With the updated user authorization model, users will no longer be able to request an account. Instead, users are authorized through the configured Authorizer implementation (it's pluggable). Consequently, we can remove all the account registration forms from the UI and OBE REST endpoints. > UI - Remove registration process > > > Key: NIFI-1928 > URL: https://issues.apache.org/jira/browse/NIFI-1928 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > With the updated user authorization model, users will no longer be able to > request an account. Instead, users are authorized through the configured > Authorizer implementation (it's pluggable). Consequently, we can remove all > the account registration forms from the UI and OBE REST endpoints. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1928) UI - Remove registration process
Matt Gilman created NIFI-1928: - Summary: UI - Remove registration process Key: NIFI-1928 URL: https://issues.apache.org/jira/browse/NIFI-1928 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Fix For: 1.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1801) Scope Templates by Process Group
[ https://issues.apache.org/jira/browse/NIFI-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15302864#comment-15302864 ] Matt Gilman commented on NIFI-1801: --- Reopened to address client-side aspects of this feature. > Scope Templates by Process Group > > > Key: NIFI-1801 > URL: https://issues.apache.org/jira/browse/NIFI-1801 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > - Update framework to manage Templates according to Process Group > - Update template persistence so they are managed by Process Group -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (NIFI-1801) Scope Templates by Process Group
[ https://issues.apache.org/jira/browse/NIFI-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reopened NIFI-1801: --- > Scope Templates by Process Group > > > Key: NIFI-1801 > URL: https://issues.apache.org/jira/browse/NIFI-1801 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > - Update framework to manage Templates according to Process Group > - Update template persistence so they are managed by Process Group -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-1801) Scope Templates by Process Group
[ https://issues.apache.org/jira/browse/NIFI-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-1801: - Assignee: Matt Gilman > Scope Templates by Process Group > > > Key: NIFI-1801 > URL: https://issues.apache.org/jira/browse/NIFI-1801 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > - Update framework to manage Templates according to Process Group > - Update template persistence so they are managed by Process Group -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (NIFI-1800) Scope Controller Services by Process Group
[ https://issues.apache.org/jira/browse/NIFI-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman reassigned NIFI-1800: - Assignee: Matt Gilman > Scope Controller Services by Process Group > -- > > Key: NIFI-1800 > URL: https://issues.apache.org/jira/browse/NIFI-1800 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core Framework, Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > > - Update framework to manage Controller Services by Process Group > - Update Controller Service persistence to include Process Group -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1914) Update framework method to use Java 8 where appropriate
Matt Gilman created NIFI-1914: - Summary: Update framework method to use Java 8 where appropriate Key: NIFI-1914 URL: https://issues.apache.org/jira/browse/NIFI-1914 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Matt Gilman Priority: Trivial Fix For: 1.0.0 Currently, there are a number methods for finding all of a given component. We should consider refactoring these to support Predicate's. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (NIFI-1781) Update UI to reflect component level authorization
[ https://issues.apache.org/jira/browse/NIFI-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-1781: -- Attachment: 0001-NIFI-1781.patch GitHub PR is currently unavailable. Posting patch here as a workaround. > Update UI to reflect component level authorization > -- > > Key: NIFI-1781 > URL: https://issues.apache.org/jira/browse/NIFI-1781 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman > Fix For: 1.0.0 > > Attachments: 0001-NIFI-1781.patch, nifi-component-samples.png, > nifi-sample-flow.png > > > - Update to UI to visual access level per component -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1906) UI - Toolbox Icons for hover and draggable
Matt Gilman created NIFI-1906: - Summary: UI - Toolbox Icons for hover and draggable Key: NIFI-1906 URL: https://issues.apache.org/jira/browse/NIFI-1906 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Priority: Minor Fix For: 1.0.0 Would be nice to include a different icon for the toolbox icon's that we would show on hover and while dragging. The new icon should provide some texture to indicate its ability to drag and drop and some indication that it will create a new component (like the + on the new Connection handle). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1901) Restore access control unit tests
Matt Gilman created NIFI-1901: - Summary: Restore access control unit tests Key: NIFI-1901 URL: https://issues.apache.org/jira/browse/NIFI-1901 Project: Apache NiFi Issue Type: Sub-task Components: Core Framework Reporter: Matt Gilman Priority: Critical Fix For: 1.0.0 The previous access control tests have been ignored as they are designed the around role based authorities. New, more comprehensive, tests need to be introduced once the fine-grained component authorization is in place. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (NIFI-1864) Processor configuration dialog box goes out of screen when clicking on a process on canvas boundaries
[ https://issues.apache.org/jira/browse/NIFI-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286579#comment-15286579 ] Matt Gilman edited comment on NIFI-1864 at 5/17/16 1:08 PM: [~rkarthi...@gmail.com] Looks great! I've merged the two patches into 0.x and master branches. Just FYI, I made a couple minor tweaks (whitespaces, semi-colon's, etc) before I merged. was (Author: mcgilman): [~rkarthi...@gmail.com] Looks great! I've merged the two patch into 0.x and master branches. Just FYI, I made a couple minor tweaks (whitespaces, semi-colon's, etc) before I merged. > Processor configuration dialog box goes out of screen when clicking on a > process on canvas boundaries > - > > Key: NIFI-1864 > URL: https://issues.apache.org/jira/browse/NIFI-1864 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 0.6.1 >Reporter: Karthik Narayanan >Assignee: Karthik Narayanan >Priority: Minor > Labels: patch, patch-available, ui, web > Fix For: 1.0.0, 0.7.0 > > Attachments: after_fix.png, before_fix_0.6.1.png, > fix_1864_0.x_patch.zip, fix_1864_1.x_patch.zip > > > I was trying to create a few flows, when i noticed that the popup dialog > (when we right click on a processor) for process configuration does not get > completely rendered inside the canvas. This happens when the process is right > on the edge of the visible portion of the canvas. The dialog gets hidden > behind the browser window and the menu option are not accesible. You have > close the menu pan the canvas and then right click on the processor to get > the context menu completely with the browser window. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (NIFI-1864) Processor configuration dialog box goes out of screen when clicking on a process on canvas boundaries
[ https://issues.apache.org/jira/browse/NIFI-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286579#comment-15286579 ] Matt Gilman commented on NIFI-1864: --- [~rkarthi...@gmail.com] Looks great! I've merged the two patch into 0.x and master branches. Just FYI, I made a couple minor tweaks (whitespaces, semi-colon's, etc) before I merged. > Processor configuration dialog box goes out of screen when clicking on a > process on canvas boundaries > - > > Key: NIFI-1864 > URL: https://issues.apache.org/jira/browse/NIFI-1864 > Project: Apache NiFi > Issue Type: Bug > Components: Core UI >Affects Versions: 0.6.1 >Reporter: Karthik Narayanan >Assignee: Karthik Narayanan >Priority: Minor > Labels: patch, patch-available, ui, web > Attachments: after_fix.png, before_fix_0.6.1.png, > fix_1864_0.x_patch.zip, fix_1864_1.x_patch.zip > > > I was trying to create a few flows, when i noticed that the popup dialog > (when we right click on a processor) for process configuration does not get > completely rendered inside the canvas. This happens when the process is right > on the edge of the visible portion of the canvas. The dialog gets hidden > behind the browser window and the menu option are not accesible. You have > close the menu pan the canvas and then right click on the processor to get > the context menu completely with the browser window. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (NIFI-1883) Controller Service referencing components
Matt Gilman created NIFI-1883: - Summary: Controller Service referencing components Key: NIFI-1883 URL: https://issues.apache.org/jira/browse/NIFI-1883 Project: Apache NiFi Issue Type: Bug Components: Core Framework Reporter: Matt Gilman Fix For: 1.0.0 Controller Service referencing components are not restored at start up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
