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

Mark Payne commented on NIFI-1280:
----------------------------------

I've created a PR that I think is sufficient. There are a few more things that 
I would like to do, but this has dragged on long enough without me pushing 
anything, so I've pushed a PR so that people can review & hopefully get merged. 
Will create separate JIRA's for the remaining enhances that I would like to 
perform. The most significant is to allow more flexibility in choosing the 
schema to use. Rather than requiring a Schema Name be provided with a Schema 
registry would like to allow user to use an attribute or read schema from the 
content of the FlowFile itself in cases such as Avro. In addition, I want to 
add updates to include the schema on the outgoing records when appropriate.

> Create QueryFlowFile Processor
> ------------------------------
>
>                 Key: NIFI-1280
>                 URL: https://issues.apache.org/jira/browse/NIFI-1280
>             Project: Apache NiFi
>          Issue Type: Task
>          Components: Extensions
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>             Fix For: 1.2.0
>
>
> We should have a Processor that allows users to easily filter out specific 
> columns from CSV data. For instance, a user would configure two different 
> properties: "Columns of Interest" (a comma-separated list of column indexes) 
> and "Filtering Strategy" (Keep Only These Columns, Remove Only These Columns).
> We can do this today with ReplaceText, but it is far more difficult than it 
> would be with this Processor, as the user has to use Regular Expressions, 
> etc. with ReplaceText.
> Eventually a Custom UI could even be built that allows a user to upload a 
> Sample CSV and choose which columns from there, similar to the way that Excel 
> works when importing CSV by dragging and selecting the desired columns? That 
> would certainly be a larger undertaking and would not need to be done for an 
> initial implementation.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to