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 2020/01/27 16:01:00 UTC
[jira] [Commented] (NIFI-7069) Groovy scripts no longer have access
to date utilities
[ https://issues.apache.org/jira/browse/NIFI-7069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024449#comment-17024449 ]
Matt Burgess commented on NIFI-7069:
------------------------------------
Workaround/improvement explained here, but we should include the module anyway to maintain current behavior/capability: https://www.baeldung.com/groovy-string-to-date
> Groovy scripts no longer have access to date utilities
> ------------------------------------------------------
>
> Key: NIFI-7069
> URL: https://issues.apache.org/jira/browse/NIFI-7069
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Matt Burgess
> Priority: Major
>
> As of NiFi 1.10 (via NIFI-5254), the version of Groovy included with NiFi is 2.5.0. There was a breaking change in that version where the date utilities (such as GDK java.util.Date.parse()) were moved into a separate module that is not included by default with the groovy-all module.
> This module is now missing from the NiFi Groovy components and thus any script using those classes/methods will fail: http://groovy-lang.org/releasenotes/groovy-2.5.html#Groovy2.5releasenotes-Breakingchanges
> The dateutil (and possibly other) Groovy modules should be included as dependencies in the groovy bundles (nifi-groovyx-bundle, nifi-scripting-bundle, possibly the groovy plugin for unit tests, etc.)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)