[
https://issues.apache.org/jira/browse/NIFI-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983351#comment-15983351
]
ASF subversion and git services commented on NIFI-3734:
-------------------------------------------------------
Commit 49a62448ce397aa7719b556c26742b8193be281e in nifi's branch
refs/heads/master from [~mattyb149]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=49a6244 ]
NIFI-3734: Add ScriptedReader and ScriptedRecordSetWriter
This closes #1691.
Signed-off-by: Andy LoPresto <[email protected]>
> 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
>
> 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)
