[
https://issues.apache.org/jira/browse/CAMEL-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566268#comment-13566268
]
Willem Jiang commented on CAMEL-5971:
-------------------------------------
It's not a common practice that we close the HDFS OutputStream and try to
append the data later.
It could more easy to make the data is consistent if we just make sure the file
is visible for the other parties when the stream is closed.
Here is a page[1] to explain this.
I think when we provide the option of closeStream, I don't think we need to
check the append option at the same time.
[1]http://blog.cloudera.com/blog/2009/07/file-appends-in-hdfs/
> HdfsOutputStream is not closing
> -------------------------------
>
> Key: CAMEL-5971
> URL: https://issues.apache.org/jira/browse/CAMEL-5971
> Project: Camel
> Issue Type: Bug
> Components: camel-hdfs
> Affects Versions: 2.10.3
> Reporter: Joe Luo
> Assignee: Willem Jiang
> Fix For: 2.10.4, 2.11.0
>
>
> I have a simple camel route that takes file from a camel-file consumer
> endpoint and sends to a camel-hdfs producer endpoint:
> <from uri="file:/local/workspace/inbox?delete=true"/>
> <to uri="hdfs://localhost:9000/local/workspace/outbox/file1"/>
> However, my Hadoop server only creates a zero length file "file1.opened"
> unless I stop camel route or a splitting condition is met with a
> "splitStratedy" option added to URI. In above cases, a file called "file1" is
> created with proper contents and the "file1.opened" is disappeared.
> It looks like that close() function of HdfsOutputStream is never called
> unless the camel route/context is stopping or we are splitting the file by
> looking at source code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
