[
https://issues.apache.org/jira/browse/NIFI-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983354#comment-15983354
]
ASF GitHub Bot commented on NIFI-3734:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1691
I reviewed, checked `contrib-check`, ran the tests, deployed to an
instance, and modified some Groovy code inside the reader and writer
definitions. Everything looked great. +1, merged.
> Add ScriptedReader and ScriptedRecordSetWriter
> ----------------------------------------------
>
> Key: NIFI-3734
> URL: https://issues.apache.org/jira/browse/NIFI-3734
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Affects Versions: 1.2.0
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> With the advent of the record/serialization framework and processors, it
> would be nice to have implementations where the user could script the
> reader/writer using the same scripting capabilities that are in the scripting
> NAR (enabling ExecuteScript, InvokeScriptedProcessor, and
> ScriptedReportingTask). This would allow for prototyping of record
> readers/writers for which there are not yet full implementations in NiFi
> (XML, e.g.)
> These scripted record handlers would not (easily) be able to leverage the
> SchemaRegistry for schema management; although the SchemaRegistry interface
> is in an API JAR, there are many utilities, base classes, etc. that are in
> the services NAR. Instead the scripted reader/writer would be responsible for
> determining the schema, perhaps by letting the user set dynamic properties,
> e.g.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
