[
https://issues.apache.org/jira/browse/NIFI-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15982350#comment-15982350
]
ASF GitHub Bot commented on NIFI-3734:
--------------------------------------
GitHub user mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/1691
NIFI-3734: Add ScriptedReader and ScriptedRecordSetWriter
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [x] Is your initial contribution a single, squashed commit?
### For code changes:
- [x] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattyb149/nifi scripted-record
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1691.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1691
----
commit cfa944364227d32244645dfd8ff188b9a9fb5e5f
Author: Matt Burgess <[email protected]>
Date: 2017-04-25T04:38:14Z
NIFI-3734: Add ScriptedReader and ScriptedRecordSetWriter
----
> 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)
