[
https://issues.apache.org/jira/browse/NIFI-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739249#comment-14739249
]
Ryan Blue commented on NIFI-919:
--------------------------------
bq. I'd rather have the warning to avoid telling someone after the fact that
they ought not have hooked up bare records up to HDFS put processor.
That's fair, but I'd rather take care of this in documentation for the bare
records option. We have to rely on users to understand what the configuration
they choose does. What if someone uses the SplitText to create individual CSV
records? We don't warn in that case that they don't want to put the result
directly into HDFS. I don't think we need to here, either.
I guess there is a difference in that the CSV case results in small, but
readable, files. We could take a look at AVRO-1704 (a standardized single
record encoding) to avoid that problem.
> Support Splitting Avro Files
> ----------------------------
>
> Key: NIFI-919
> URL: https://issues.apache.org/jira/browse/NIFI-919
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Priority: Minor
> Fix For: 0.4.0
>
> Attachments: NIFI-919-2.patch, NIFI-919.patch
>
>
> Provide a processor that splits an Avro file into multiple smaller files.
> Would be nice to have a configurable batch size so a user could produce
> single record files and also multi-record files of smaller size than the
> original. Also consider making the output format configurable, data file vs
> bare record.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
