[
https://issues.apache.org/jira/browse/NIFI-7343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17742571#comment-17742571
]
ASF subversion and git services commented on NIFI-7343:
-------------------------------------------------------
Commit 21e5ebc840a5e5149f83a3de98e41df0ed999d05 in nifi's branch
refs/heads/main from Matt Burgess
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=21e5ebc840 ]
NIFI-7343: Add support for SchemaRegistryService to scripted components
This closes #7467
Signed-off-by: David Handermann <[email protected]>
> 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
> Fix For: 1.latest, 2.latest
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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.20.10#820010)
