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

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

Github user aperepel commented on the pull request:

    https://github.com/apache/nifi/pull/420#issuecomment-221625867
  
    My only driver was going with something which wasn't abandoned and had 
recent release activity (who would've thought, that pesky CSV problem... :) )
    
    I was just pointed to this effort this morning, can't yet comment on how 
portable the OpenCSV use is (please, let it not stop the PR from moving forward 
- I'd rather refactor in the next release than hold off).
    
    There are other interesting ideas circulating around CSV, which may depend 
on yet another, third library. For now flagging this with the Calcite team an 
area to collaborate on is fine, IMHO.


> 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