[jira] [Updated] (NIFI-950) Perform component validation asynchronously

[ https://issues.apache.org/jira/browse/NIFI-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-950: - Description: I created a flow that is a self referencing http loop. The flow was working fine but I wanted

[jira] [Updated] (NIFI-950) Perform component validation asynchronously

[ https://issues.apache.org/jira/browse/NIFI-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-950: - Description: I created a flow that is a self referencing http loop. The flow was working fine but I wanted

[jira] [Commented] (NIFI-950) After importing a template parts of UI become very slow

[ https://issues.apache.org/jira/browse/NIFI-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742448#comment-14742448 ] Matt Gilman commented on NIFI-950: -- Yeah, we'll have to evaluate our options. It becomes non trivial when

[jira] [Commented] (NIFI-950) Perform component validation asynchronously

[ https://issues.apache.org/jira/browse/NIFI-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742531#comment-14742531 ] Joseph Percivall commented on NIFI-950: --- The core problem is that when there is controller that takes

[jira] [Updated] (NIFI-950) Perform component validation asynchronously

[ https://issues.apache.org/jira/browse/NIFI-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-950: - Summary: Perform component validation asynchronously (was: After importing a template parts of UI become

[jira] [Updated] (NIFI-950) Perform component validation asynchronously

[ https://issues.apache.org/jira/browse/NIFI-950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-950: - Issue Type: Improvement (was: Bug) > Perform component validation asynchronously >

[jira] [Commented] (NIFI-950) After importing a template parts of UI become very slow

[ https://issues.apache.org/jira/browse/NIFI-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742446#comment-14742446 ] Joseph Witt commented on NIFI-950: -- So the dev advice is good. But the ui needs to remain responsive.

[jira] [Commented] (NIFI-817) Create Processors to interact with HBase

[ https://issues.apache.org/jira/browse/NIFI-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742665#comment-14742665 ] Mark Payne commented on NIFI-817: - Alan, GetHBase is indeed intended for incremental updates. As-is, it is

[2/2] nifi git commit: NIFI-948: Provide capability to register notifications for nifi lifecycle events

NIFI-948: Provide capability to register notifications for nifi lifecycle events Project: http://git-wip-us.apache.org/repos/asf/nifi/repo Commit: http://git-wip-us.apache.org/repos/asf/nifi/commit/992e8410 Tree: http://git-wip-us.apache.org/repos/asf/nifi/tree/992e8410 Diff:

[1/2] nifi git commit: NIFI-948: Provide capability to register notifications for nifi lifecycle events

Repository: nifi Updated Branches: refs/heads/master 4a7d1fe61 -> 992e84102 http://git-wip-us.apache.org/repos/asf/nifi/blob/992e8410/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-resources/src/main/resources/conf/bootstrap.conf

[jira] [Commented] (NIFI-818) Create Processors for interacting with Accumulo

[ https://issues.apache.org/jira/browse/NIFI-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742742#comment-14742742 ] Mark Payne commented on NIFI-818: - [~pinkdevelops] - There is a PutAccumuloCell processor that I have

[jira] [Updated] (NIFI-761) Have provenance event search times be based off "now"

[ https://issues.apache.org/jira/browse/NIFI-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aldrin Piri updated NIFI-761: - Summary: Have provenance event search times be based off "now" (was: Have provenance event search end time