[
https://issues.apache.org/jira/browse/NIFI-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445405#comment-17445405
]
ASF subversion and git services commented on NIFI-5821:
-------------------------------------------------------
Commit d66219739bce8cb585e5a9890c6e15a138c3598e in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=d662197 ]
NIFI-5821 Added Engine Name to Script Engine property descriptions
Signed-off-by: Matthew Burgess <mattyb...@apache.org>
This closes #5529
> 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: Improvement
> Affects Versions: 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.7.1, 1.15.0
> Reporter: Ryan Hendrickson
> Assignee: David Handermann
> Priority: Major
> Attachments: image-2018-11-15-00-37-05-004.png
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> ExecuteScript drop-down should say "jython" or "Python (jython)" ...
> Something to indicate it is running jython.
> 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)
