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

Invalidate instead of evaluating empty script in scripted components

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.14.0
    • Component/s: Extensions
    • Labels:
      None

      Description

      As of NIFI-8625, script engines that aren't Invocable are filtered out from the list of available engines to choose for most scripting components (except for ExecuteScript and ScriptedTransformRecord at the time of this writing) as all other scripting components require an Invocable script engine. However this causes ECMAScript to be the default engine, and it throws a NullPointerException when the script body is empty (which it is when the processor is first created).

      Rather than make a different engine be the default (which could be done under a different Jira), it is better to not try to create the ScriptRunner and/or evaluate the script if the body is empty.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mattyb149 Matt Burgess
                Reporter:
                mattyb149 Matt Burgess
              • Votes:
                0 Vote for this issue
                Watchers:
                2 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 - 20m
                  20m