You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Matt Burgess (JIRA)" <ji...@apache.org> on 2019/04/04 13:28:00 UTC

[jira] [Updated] (NIFI-6186) JythonScriptEngineConfigurator fails to account for Python escaping in Module Directory property

     [ https://issues.apache.org/jira/browse/NIFI-6186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Burgess updated NIFI-6186:
-------------------------------
    Status: Patch Available  (was: Open)

> JythonScriptEngineConfigurator fails to account for Python escaping in Module Directory property
> ------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-6186
>                 URL: https://issues.apache.org/jira/browse/NIFI-6186
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Andrew Mathis
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, JythonScriptEngineConfigurator (in its init() method) incorporates the module directory list (as derived from the Module Directory property value) into evaluated Jython code as string literals without any regard to how the paths will be interpreted in Jython. This means that Module Directory paths that include Jython escape sequences (e.g. "\a", "\1") will be mis-interpreted in Jython execution. Rather than interpreting paths directly as Python string literals, a method like PyString.encode_UnicodeEscape should be used to translate the Java strings into appropriate Jython string literals.
> This issue will be especially relevant in Windows, where paths will often contain backslashes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)