[
https://issues.apache.org/jira/browse/NIFI-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15954024#comment-15954024
]
Mark Payne commented on NIFI-1280:
----------------------------------
I am getting pretty close to this being in good shape now. It's taken far
longer than I ever expected, but that's because it's really been transforming a
lot of how we handle different data formats in the process. It's really
incorporated most all of the features proposed in
https://cwiki.apache.org/confluence/display/NIFI/First-class+Avro+Support and
fairly extensive mailing list conversations that have occurred around
record-oriented data here:
http://apache-nifi-developer-list.39713.n7.nabble.com/Looking-for-feedback-on-my-WIP-Design-td13097.html#none
and in a couple of other emails. I need to do some cleanup and then I think I
can get a PR in this week. I need to write some more unit tests and ensure that
we are handling data type coercion consistently across the different
readers/writers. I also need to update a bit how we are referencing schemas
when appropriate.
With these Record Readers and Writers, I think we can actually remove the
TransformXToY processors that were brought in recently in the
nifi-registry-processors module. [~ozhurakousky] do you agree?
> 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)
