[ 
https://issues.apache.org/jira/browse/NIFI-7242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Payne reassigned NIFI-7242:
--------------------------------

    Assignee: Mark Payne

> Parameters update not taken into account in controller services
> ---------------------------------------------------------------
>
>                 Key: NIFI-7242
>                 URL: https://issues.apache.org/jira/browse/NIFI-7242
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>            Reporter: Pierre Villard
>            Assignee: Mark Payne
>            Priority: Blocker
>             Fix For: 1.12.0, 1.11.4
>
>         Attachments: parametersIssue.xml
>
>
> There is a bug with the parameters when used in Controller Services:
>  * when updating a parameter that is referenced in a controller service (in 
> this case avro schema registry), changing the value of the parameter does not 
> seem to trigger the restart of the controller service
>  * even if I do restart the components manually, the old value of the 
> parameter is still used... NiFi restart is the only way to get the new value 
> applied
> With the supplied template, create a Parameter Context with schema =
> {code:java}
> {
>   "type" : "record",
>   "name" : "myData",
>   "namespace" : "myLine",
>   "fields" : [
>     {
>       "name" : "myField1",
>       "type" : "string"
>     }
>   ]
> }
> {code}
> The AvroSchemaRegistry contains the schema with:
> schema => #\{schema}
> Get everything running: output data has only one column. Then update the 
> Parameter Context to have schema =
> {code:java}
> {
>   "type" : "record",
>   "name" : "myData",
>   "namespace" : "myLine",
>   "fields" : [
>     {
>       "name" : "myField1",
>       "type" : "string"
>     }, {
>       "name" : "myField2",
>       "type" : "string"
>     }
>   ]
> }
> {code}
> Output data has still one column only when it should have two with the new 
> schema.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to