Skip to content

NIFI-3222 - Allow ExecuteScript to use ExpressionLanguage to define …#1640

Closed
trixpan wants to merge 1 commit intoapache:masterfrom
trixpan:NIFI-3222
Closed

NIFI-3222 - Allow ExecuteScript to use ExpressionLanguage to define …#1640
trixpan wants to merge 1 commit intoapache:masterfrom
trixpan:NIFI-3222

Conversation

@trixpan
Copy link
Contributor

@trixpan trixpan commented Mar 31, 2017

…the scripting engine modules path

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

  • Is there a JIRA ticket associated with this PR? Is it referenced
    in the commit message?

  • Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

  • Has your PR been rebased against the latest commit within the target branch (typically master)?

  • Is your initial contribution a single, squashed commit?

For code changes:

  • Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
  • ~~~Have you written or updated unit tests to verify your changes?~~~
  • ~~~If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?~~~
  • ~~~If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?~~~
  • ~~~If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?~~~
  • ~~~If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?~~~

For documentation related changes:

  • ~~~Have you ensured that format looks appropriate for the output in which it is rendered?~~~

Note:

Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@trixpan
Copy link
Contributor Author

trixpan commented Mar 31, 2017

@mattyb149 Would you be able to give me a hand with this PR?

Cheers!

@mattyb149
Copy link
Contributor

Code LGTM, my comments would be to add this same improvement to InvokeScriptedProcessor, and update one unit test apiece to use Expression Language to set the Module Directory property, to prove that this works

@trixpan
Copy link
Contributor Author

trixpan commented Mar 31, 2017

fair enough. will do both

@mattyb149
Copy link
Contributor

And there's a typo in Language in the commit/PR title ;)

@trixpan trixpan changed the title NIFI-3222 - Allow ExecuteScript to use ExpressionLangugage to define … NIFI-3222 - Allow ExecuteScript to use ExpressionLanguage to define … Mar 31, 2017
…eporting

            to use ExpressionLanguage to define the scripting engine modules path
@trixpan
Copy link
Contributor Author

trixpan commented Apr 1, 2017

@mattyb149 - should be all goody now

@mattyb149
Copy link
Contributor

+1 LGTM, Built and ran unit tests, ran NiFi with ExecuteScript using EL for Module Directory, everything looks good. Thanks much for the improvement! Merging to master

@asfgit asfgit closed this in 84f1fb3 Apr 1, 2017
@trixpan trixpan deleted the NIFI-3222 branch April 1, 2017 06:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants