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

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

Github user markap14 commented on the pull request:

    https://github.com/apache/nifi/pull/420#issuecomment-218563978
  
    Excellent. Yes, I'm thinking potentially Avro, JSON, Parquet... perhaps 
others. For 0.7.0 we may only have CSV and perhaps JSON but will have things in 
place to add more. I know a couple of people who I've recently learned are 
actually Calcite contributors / PMC members who may also be able to provide 
some guidance to me, so we can make this pretty awesome. You've provided a 
phenomenally awesome start! It is much appreciated!


> Create FilterCSVColumns 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: Toivo Adams
>
> 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.4#6332)

Reply via email to