You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Ben O'Day (JIRA)" <ji...@apache.org> on 2013/11/07 15:27:18 UTC
[jira] [Resolved] (CAMEL-6864) camel-hdfs - split by BYTES or
MESSAGES has dependent configs
[ https://issues.apache.org/jira/browse/CAMEL-6864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ben O'Day resolved CAMEL-6864.
------------------------------
Resolution: Not A Problem
alright, will just update the wiki until I get further input on this...
> camel-hdfs - split by BYTES or MESSAGES has dependent configs
> -------------------------------------------------------------
>
> Key: CAMEL-6864
> URL: https://issues.apache.org/jira/browse/CAMEL-6864
> Project: Camel
> Issue Type: Bug
> Components: camel-hdfs
> Affects Versions: 2.10.4, 2.11.0
> Reporter: Ben O'Day
> Assignee: Ben O'Day
> Priority: Minor
> Fix For: Future
>
>
> per the discussion/changes in CAMEL-5971...
> currently, if only the BYTES or MESSAGES split criteria is specified, then the output stream is closed with every message and creates a new file for subsequent messages regardless of BYTES/MESSAGES written to the file...
> that said, if used along with the IDLE config or by setting the header HdfsConstants.HDFS_CLOSE=false...it does work fine
> so, we should either update the wiki to reflect this (if 'as designed') or update the HdfsProducer to not close the stream in the absence of the IDLE config (rely only on the split logic, HdfsConstants.HDFS_CLOSE=true header or route stop to close the stream)
--
This message was sent by Atlassian JIRA
(v6.1#6144)