[
https://issues.apache.org/jira/browse/NIFI-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15300284#comment-15300284
]
ASF GitHub Bot commented on NIFI-1280:
--------------------------------------
Github user julianhyde commented on the pull request:
https://github.com/apache/nifi/pull/420#issuecomment-221623264
@joewitt I agree with your philosophy... however sometimes the other
project didn't put as much thought into the decision as you imagine. A little
bit of polite back-pressure sometimes helps. If you'd like Calcite to switch
from open-csv to commons-csv log a JIRA case and we'd definitely consider it.
We needn't halt the Calcite integration for this, but the next version of
Calcite might bring in one fewer external dependency.
The same goes for any other dependencies you observe in Calcite.
> 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)
