[
https://issues.apache.org/jira/browse/NIFI-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16454540#comment-16454540
]
ASF GitHub Bot commented on NIFI-4181:
--------------------------------------
Github user Wesley-Lawrence commented on the issue:
https://github.com/apache/nifi/pull/2003
@mattyb149 Looks like a lot has changed in the last 9 months.
The code I added here leveraged classes related to Schema registries, but
those classes have been moved into a more Avro specific package
(`nifi-avro-record-utils`), where the CSV stuff is still under a standard
package (`nifi-standard-record-utils`). Looks like it'll take some work to
abstract the schema-registry specific stuff away from Avro, so the CSV
reader/writers can leverage it.
Sadly, I don't have the time to get back deep in NiFi right now, so I'm OK
with closing this PR so a more updated solution can be worked on.
> CSVReader and CSVRecordSetWriter services should be able to work given an
> explicit list of columns.
> ---------------------------------------------------------------------------------------------------
>
> Key: NIFI-4181
> URL: https://issues.apache.org/jira/browse/NIFI-4181
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Wesley L Lawrence
> Priority: Minor
> Attachments: NIFI-4181.patch
>
>
> Currently, to read or write a CSV file with *Record processors, the CSVReader
> and CSVRecordSetWriters need to be given an avro schema. For CSV, a simple
> column definition can also work.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
