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/04/08 22:03:00 UTC
[jira] [Assigned] (NIFI-7343) Allow scripted components to use
Schema Registry classes and utils
[ https://issues.apache.org/jira/browse/NIFI-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Burgess reassigned NIFI-7343:
----------------------------------
Assignee: Matt Burgess
> Allow scripted components to use Schema Registry classes and utils
> -------------------------------------------------------------------
>
> Key: NIFI-7343
> URL: https://issues.apache.org/jira/browse/NIFI-7343
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
>
> When the scripted reader/writer components were added (NIFI-3734), the SchemaRegistryService class was in an implementation NAR and as such was not included in the scripting bundle. However as of NIFI-5123, SchemaRegistryService has been moved into nifi-avro-record-utils, which is a utility JAR for working with things like schema registries.
> nifi-avro-record-utils can be very useful for scripted components and should be available in the NAR for that reason.
> Also, ScriptedReader will have to be updated to call the script's "onEnabled" method if one exists. This was done for BaseScriptedLookupService for the same reason, and should be applied as part of these changes, so the SchemaRegistryService (if used) can be enabled via the script.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)