[ 
https://issues.apache.org/jira/browse/NIFI-5829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703346#comment-16703346
 ] 

ASF GitHub Bot commented on NIFI-5829:
--------------------------------------

Github user patricker commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/3188#discussion_r237530330
  
    --- Diff: 
nifi-nar-bundles/nifi-scripting-bundle/nifi-scripting-processors/src/main/java/org/apache/nifi/record/script/ScriptedRecordSetWriter.java
 ---
    @@ -60,12 +61,16 @@ public void onEnabled(final ConfigurationContext 
context) {
             super.onEnabled(context);
         }
     
    -
         @Override
         public RecordSetWriter createWriter(ComponentLog logger, RecordSchema 
schema, OutputStream out) throws SchemaNotFoundException, IOException {
    +        return createWriter(new HashMap<>(), logger, schema, out);
    --- End diff --
    
    Thanks, Updated.


> Create Lookup Controller Services for RecordSetWriter and RecordReader
> ----------------------------------------------------------------------
>
>                 Key: NIFI-5829
>                 URL: https://issues.apache.org/jira/browse/NIFI-5829
>             Project: Apache NiFi
>          Issue Type: Improvement
>            Reporter: Peter Wicks
>            Assignee: Peter Wicks
>            Priority: Minor
>
> In the same way as the new DBCP Lookup Service, create lookup services for 
> RecordSetWriter and RecordReader.
> This will help to make flows much more generic, and allow for some very 
> flexible processors.
> Example: A processor like PutDatabaseRecord will be able to push to any 
> database in any readable record format from a single processor by configuring 
> everything through the lookup services.
> Example: ConvertRecord will be able to convert from any number of various 
> input formats to a constant output format by using the RecordReader Lookup, 
> and a fixed RecordSetWriter.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to