[
https://issues.apache.org/jira/browse/CAMEL-6864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben O'Day updated CAMEL-6864:
-----------------------------
Description:
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)
was:
per the discussion/changes in CAMEL-5971...
currently, if only the BYTES or MESSAGES split criteria are specified (w/o
using IDLE or setting HdfsConstants.HDFS_CLOSE=false), 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...
we should either update the wiki to reflect this (if this is simply '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)
Summary: camel-hdfs - split by BYTES or MESSAGES has dependent configs
(was: camel-hdfs - split by BYTES/MESSAGES only works when IDLE/header is
specified)
> 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)
