[
https://issues.apache.org/jira/browse/NIFI-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14742448#comment-14742448
]
Matt Gilman commented on NIFI-950:
----------------------------------
Yeah, we'll have to evaluate our options. It becomes non trivial when
validation is dependent on the environment. We don't know when it's finished
validation nor will we know if it needs to be re-validate. The only thing that
does know this is the processor itself which is why it's always been done there.
> After importing a template parts of UI become very slow
> -------------------------------------------------------
>
> Key: NIFI-950
> URL: https://issues.apache.org/jira/browse/NIFI-950
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: Joseph Percivall
> Attachments: self_reference_flow_fix.xml
>
>
> I created a flow that is a self referencing http loop. The flow was working
> fine but I wanted to save the template for later testing. I downloaded the
> the flow as a template. Then I tried testing a thread.sleep in the beginning
> of onConfigured, createSSLContext, and validate methods of
> StandardSSLContextService. I did a mvn clean install in the
> nifi-nar-bundles/nifi-standard-services/nifi-ssl-context-bundle/nifi-ssl-context-service
> directory. Then a mvn clean install in the nifi-assembly directory. After I
> imported the template the UI became very slow when clicking to different
> windows of the UI such as configuring a processor and the controller services
> window.
> I then stashed my changes and rebuilt the files. Once again I imported my
> template, and attempting to configure a processor or accessing the controller
> services window became very slow.
> The flow xml is attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
