Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-7242

Parameters update not taken into account in controller services

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • None
    • 1.12.0, 1.11.4
    • Core Framework
    • None

    Description

      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 =

      {
        "type" : "record",
        "name" : "myData",
        "namespace" : "myLine",
        "fields" : [
          {
            "name" : "myField1",
            "type" : "string"
          }
        ]
      }
      

      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 =

      {
        "type" : "record",
        "name" : "myData",
        "namespace" : "myLine",
        "fields" : [
          {
            "name" : "myField1",
            "type" : "string"
          }, {
            "name" : "myField2",
            "type" : "string"
          }
        ]
      }
      

      Output data has still one column only when it should have two with the new schema.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            markap14 Mark Payne
            pvillard Pierre Villard
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 1h
                1h

                Slack

                  Issue deployment