[
https://issues.apache.org/jira/browse/NIFI-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758561#comment-16758561
]
ASF subversion and git services commented on NIFI-5995:
-------------------------------------------------------
Commit fef41b302216934886817fd9335ea4b5d62c4c1e in nifi's branch
refs/heads/master from Mike Thomsen
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=fef41b3 ]
NIFI-5995 Updated ScriptedLookupService documentation to warn about Jython and
removed Jython from the list of supported script engines for it because it's
broken now.
Signed-off-by: Matthew Burgess <[email protected]>
This closes #3287
> Update ScriptedLookupService documentation about Jython issues
> --------------------------------------------------------------
>
> Key: NIFI-5995
> URL: https://issues.apache.org/jira/browse/NIFI-5995
> Project: Apache NiFi
> Issue Type: Task
> Reporter: Mike Thomsen
> Assignee: Mike Thomsen
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> From nifi-user:
> {quote}Short answer: Unfortunately this is not currently possible for Jython
> in NiFi 1.7.0+ because of a Jython bug [1] that never made it into a
> release.
>
> Longer answer: NIFI-5287 [2], released as part of NiFi 1.7.0,
> introduced a new default interface method for LookupService, in order
> to avoid breaking API compatibility for those with custom
> LookupServices. This exposes the bug in [1] for the Jython script
> engine. At a major release point (NiFi 2.0) we could refactor the NiFi
> codebase to remove the default interface method, update all internal
> implementations, and announce that the LookupService API has changed
> and thus custom implementations would have to be updated. Not sure if
> we can get away with that for minor releases or not, usually breaking
> API compatibility is a no-no except for major releases.
> {quote}
> [1] [https://bugs.jython.org/issue2403]
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
