[jira] [Resolved] (CAMEL-6028) camel-hdfs - Support CamelFileName to write to a new file, when not using split strategy

2013-10-17 Thread Ben O'Day (JIRA)

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

Ben O'Day resolved CAMEL-6028.
--

Resolution: Fixed

added Expression support in Commit: 4c3d1526c9d285e138a16b9fd275171f4255ec65

> camel-hdfs - Support CamelFileName to write to a new file, when not using 
> split strategy
> 
>
> Key: CAMEL-6028
> URL: https://issues.apache.org/jira/browse/CAMEL-6028
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-hdfs
>Reporter: Claus Ibsen
>Assignee: Ben O'Day
> Fix For: 2.13.0
>
>
> When using camel-hdfs to write to files, without using split strategy. Then 
> the file is always the same which is the file configured on the endpoint.
> We should add support for the CamelFileName header so you can give the file a 
> new name, relative to the endpoint configuration. Then it works more like the 
> file producer would do.



--
This message was sent by Atlassian JIRA
(v6.1#6144)


[jira] [Resolved] (CAMEL-6028) camel-hdfs - Support CamelFileName to write to a new file, when not using split strategy

2013-10-16 Thread Ben O'Day (JIRA)

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

Ben O'Day resolved CAMEL-6028.
--

Resolution: Fixed

added support for this in commit: de4cb2b98259fb7c9777e8c0ca79f841956b9994



> camel-hdfs - Support CamelFileName to write to a new file, when not using 
> split strategy
> 
>
> Key: CAMEL-6028
> URL: https://issues.apache.org/jira/browse/CAMEL-6028
> Project: Camel
>  Issue Type: Improvement
>  Components: camel-hdfs
>Reporter: Claus Ibsen
>Assignee: Ben O'Day
> Fix For: 2.13.0
>
>
> When using camel-hdfs to write to files, without using split strategy. Then 
> the file is always the same which is the file configured on the endpoint.
> We should add support for the CamelFileName header so you can give the file a 
> new name, relative to the endpoint configuration. Then it works more like the 
> file producer would do.



--
This message was sent by Atlassian JIRA
(v6.1#6144)