[
https://issues.apache.org/jira/browse/NIFI-6496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896266#comment-16896266
]
Bryan Bende commented on NIFI-6496:
-----------------------------------
[~bickerx2] I think the solution being discussed by [~malthe] and
[~ijokarumawak] is more specific to the record processors, and wouldn't
involved any changes to the repos or NiFi internals. Basically just decorators
for the record readers/writers that a user has to opt into using.
Every record processor could continue to be used as it is today where it
directly uses a real record reader like XML, CSV, JSON, etc. ... OR it could
wrap the real record reader in a decompression reader first, but it would be
the user configuring all of this. I tried to show an example setup in my
previous comment.
> Add compression support to record reader processor
> --------------------------------------------------
>
> Key: NIFI-6496
> URL: https://issues.apache.org/jira/browse/NIFI-6496
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Malthe Borch
> Priority: Minor
> Labels: easyfix, usability
>
> Text-based record formats such as CSV, JSON and XML compress well and will
> often be transmitted in a compressed format. If compression support is added
> to the relevant processors, users will not need to explicitly unpack files
> before processing (which may not be feasible or practical due to space
> requirements).
> There are at least two ways of implementing this, using either a generic
> approach where a {{CompressedRecordReaderFactory}} is the basis for a new
> controller service that wraps the underlying record reader controller service
> (e.g. {{CSVReader}}); or adding the functionality at the relevant record
> reader implementations.
> The latter option may provide a better UX because no additional
> {{ControllerService}} has to be configured.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
