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

Improve flow behavior on refactored processor names/packages

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 1.0.0, 1.0.0-Beta
    • Core Framework
    • None

    Description

      My case is simple and easy to reproduce:
      1. Create a flow with custom processor (e.g. abc.MyProcesser )
      2. Make sure flow is working. Then stop the server.
      3. Replace nar in lib with new nar after refactoring processor's package (
      e.g., xzy.MyProcesser)
      4. When you try to start nifi , it fails with error in the log saying class
      not found ( obviously coz deployed flow is still looking for old class)

      My expectation is system should at least start and only throw error when
      user try to start a flow that that had reference to class(processor) which
      is no more available in the newly deployed nar.

      Attachments

        Issue Links

          Activity

            People

              markap14 Mark Payne
              xmlking sumanth chinthagunta
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: