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

Updating variables does not properly resolve referencing components causing variable updates to incorrectly fail

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.9.0, 1.9.1
    • 1.10.0
    • Core Framework
    • None

    Description

      steps to reproduce:

       

      There is attached XML template for a flow. It contains:

      • Root PG
        • variable named my_id in the variable registry
        • an updateattribute processor that references my_id
        • a nested process group
          • overrides my_id in its variable registry
          • an update attribute processor that references my_id
      1. load the template into a clean nifi
      2. start up the 2 updateattribute processors
      3. open the root PG's variable registry and attempt to change the value of variable named my_id 
      4. itll show only 1 processor references it, which is correct. 
      5. the update request will incorrectly fail as it resolves the updateattribute processor in the nested processgroup as referencing the my_id variable in the root pg, even though it is actually referencing the overridden my_id in the nested PG where it is provisioned

       

      In the update request, the first steps succeed:

      {"description": "Identifying components affected","complete": true},
      {"description": "Stopping affected Processors","complete": true},

      But the affectedComponents section of the update-request only shows 1 processor which is correct. The "Applying Updates" step of the update fails and the error message references the uuid of the processor in the nested PG which is referencing the overridden value.

      Attachments

        1. nifi_bug.xml
          18 kB
          Charlie Meyer

        Issue Links

          Activity

            People

              markap14 Mark Payne
              cemeyer2 Charlie Meyer
              Votes:
              0 Vote for this issue
              Watchers:
              3 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 - 0.5h
                  0.5h