An imported Template with a Notification Processor fails to deploy

[Chaffelson]

Notification Processors contain encrypted information, such as passwords, and when imported into a system other than the generating system that information cannot be retrieved and the Topology will fail to deploy. The Notification Processor may be removed or recreated to resolve the issue.

[arunmahadevan]

I tried exporting and importing a topology with notification sink. During export we save all configurations including the password and during import the same password value is retained. Are you observing a different behavior ?

[Chaffelson]

I last tested this in the 3.0 release code at Hadoop summit, I have not tested it again since.

The behaviour was specifically exporting from instance A and trying to import into instance B where the compiled JARs were not available - this may have been fixed in the intervening time?