[
https://issues.apache.org/jira/browse/NIFI-12531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Villard updated NIFI-12531:
----------------------------------
Fix Version/s: 2.0.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Parameter references are removed after property migration
> ---------------------------------------------------------
>
> Key: NIFI-12531
> URL: https://issues.apache.org/jira/browse/NIFI-12531
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.0.0-M1, 2.0.0
> Reporter: Zsihovszki Krisztina
> Assignee: Zsihovszki Krisztina
> Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Parameter references disappear from the properties when a flow is imported to
> NiFi 2.0.
> The problem was observed for InvokeHTTP processor when e.g. we extract "Host
> URL" property to a parameter. The flow definition contains the parameter
> reference properly:
>
> {code:java}
> "HTTP URL": "#{Server URL}",{code}
>
> but the property value is resolved in the imported flow and the connection
> between the parameter ("Server URL") and the processor is lost.
> The issue did not occur for other processors like ConvertRecord and it occurs
> in NiFi 2.0 only.
> Based on my investigation the root cause seems to be related to the property
> migration.
> During the property migration the raw values("#\{Server URL}") are resolved
> to effective values (e.g. http://host:port).
> In StandardProcessorNode.migrateProperties() the properties are overwritten (
> overwriteProperties) if the propertyConfig is modified.
> At this step the effective properties are used while I belive the raw
> properties should have been used.
> Another observed minor issue:
> In InvokeHTTP processor, the "Connection Timeout" is renamed to the same name
> (that triggered the above mentioned issue since it looked as if the processor
> properties were modified, property overwrite was needed)
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
