[
https://issues.apache.org/jira/browse/NIFI-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Hendrickson updated NIFI-5821:
-----------------------------------
Description:
Code executed in the ExecuteScript processor, when Python is selected, is
actually running as Jython. This should be made far more clear on the UI as a
user is selecting the Script Language. The only place python is made reference
to is in the tags for the processor, which also makes reference to python.
Jython datetime.datetime is not handled the same way that Python
datetime.datetime is because of mapping datetime back to Java objects in
Jython. This can cause plenty of issues, and cause Python code to need to be
modified to jython supported code.
was:
Code executed in the ExecuteScript processor, when Python is selected, is
actually running as Jython. This should be made far more clear on the UI as a
user is selecting the Script Language. The only place python is made reference
to is in the tags for the processor, which also makes reference to python.
Jython datetime.datetime is not handled the same way that Python
datetime.datetime is because of mapping datetime back to Java objects in
Jython. This can cause plenty of issues, and cause Python code to need to be
modified to jython supported code.
Additionally, there's probably a series of benefits that can be taken advantage
of if you know it's actually jython vs python.
> ExecuteScript should say Python is really Jython running
> --------------------------------------------------------
>
> Key: NIFI-5821
> URL: https://issues.apache.org/jira/browse/NIFI-5821
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.7.1
> Reporter: Ryan Hendrickson
> Priority: Major
> Attachments: image-2018-11-15-00-37-05-004.png
>
>
> Code executed in the ExecuteScript processor, when Python is selected, is
> actually running as Jython. This should be made far more clear on the UI as
> a user is selecting the Script Language. The only place python is made
> reference to is in the tags for the processor, which also makes reference to
> python.
> Jython datetime.datetime is not handled the same way that Python
> datetime.datetime is because of mapping datetime back to Java objects in
> Jython. This can cause plenty of issues, and cause Python code to need to be
> modified to jython supported code.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
