You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/01/16 10:44:13 UTC

[jira] [Updated] (CAMEL-5971) HdfsOutputStream is not closing

     [ https://issues.apache.org/jira/browse/CAMEL-5971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-5971:
-------------------------------

    Fix Version/s: 2.11.0
                   2.10.4

There is some idle task in the hdfs producer. I would assume that ought to close the stream if the producer is not busy.

Though camel-hdfs is a bit odd. I would have liked it was implemented more like camel-file etc. In fact we have another JIRA ticket about that.
                
> 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