You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/09/27 08:54:40 UTC
[jira] Created: (CAMEL-3163) Add look for mark file feature to file
consumer
Add look for mark file feature to file consumer
-----------------------------------------------
Key: CAMEL-3163
URL: https://issues.apache.org/activemq/browse/CAMEL-3163
Project: Apache Camel
Issue Type: New Feature
Components: camel-core, camel-ftp
Affects Versions: 2.4.0
Reporter: Claus Ibsen
Priority: Minor
Fix For: 2.6.0
Its still common to transfer data using files and using a marker file when the data is ready.
We should have a feature on the file consumer, so it can be used to scan for marker files, and then use the real file as the message body.
And then when its done it can delete/move both files.
The problem is how to define an easy way of correlating the marker file to the real file. We can use an Expression for that.
For example maybe something like, (use better option names)
{{realFile=${file:name.noext}.csv&filter=*.ready}}
Then Camel will react when there is a .ready file in the folder. And evaluate the expression and see if a file with that result exists.
When it's done the marker file should be deleted, and the real file should be moved using the existing options for that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (CAMEL-3163) Add look for mark file feature to file
consumer
Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-3163:
-------------------------------
Description:
Its still common to transfer data using files and using a marker file when the data is ready.
We should have a feature on the file consumer, so it can be used to scan for marker files, and then use the real file as the message body.
And then when its done it can delete/move both files.
The problem is how to define an easy way of correlating the marker file to the real file. We can use an Expression for that.
For example maybe something like, (use better option names)
{{realFile=${file:name.noext}.csv&include=.*.ready}}
Then Camel will react when there is a .ready file in the folder. And evaluate the expression and see if a file with that result exists.
When it's done the marker file should be deleted, and the real file should be moved using the existing options for that.
was:
Its still common to transfer data using files and using a marker file when the data is ready.
We should have a feature on the file consumer, so it can be used to scan for marker files, and then use the real file as the message body.
And then when its done it can delete/move both files.
The problem is how to define an easy way of correlating the marker file to the real file. We can use an Expression for that.
For example maybe something like, (use better option names)
{{realFile=${file:name.noext}.csv&filter=*.ready}}
Then Camel will react when there is a .ready file in the folder. And evaluate the expression and see if a file with that result exists.
When it's done the marker file should be deleted, and the real file should be moved using the existing options for that.
> Add look for mark file feature to file consumer
> -----------------------------------------------
>
> Key: CAMEL-3163
> URL: https://issues.apache.org/activemq/browse/CAMEL-3163
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core, camel-ftp
> Affects Versions: 2.4.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.6.0
>
>
> Its still common to transfer data using files and using a marker file when the data is ready.
> We should have a feature on the file consumer, so it can be used to scan for marker files, and then use the real file as the message body.
> And then when its done it can delete/move both files.
> The problem is how to define an easy way of correlating the marker file to the real file. We can use an Expression for that.
> For example maybe something like, (use better option names)
> {{realFile=${file:name.noext}.csv&include=.*.ready}}
> Then Camel will react when there is a .ready file in the folder. And evaluate the expression and see if a file with that result exists.
> When it's done the marker file should be deleted, and the real file should be moved using the existing options for that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (CAMEL-3163) Add look for mark file feature to
file consumer
Posted by "Julian Cable (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/CAMEL-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=62624#action_62624 ]
Julian Cable commented on CAMEL-3163:
-------------------------------------
This would be really useful.
Maybe we could have something as simple as
{{readyExt=mrk}}
But Claus' specification seems just right.
> Add look for mark file feature to file consumer
> -----------------------------------------------
>
> Key: CAMEL-3163
> URL: https://issues.apache.org/activemq/browse/CAMEL-3163
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core, camel-ftp
> Affects Versions: 2.4.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 2.6.0
>
>
> Its still common to transfer data using files and using a marker file when the data is ready.
> We should have a feature on the file consumer, so it can be used to scan for marker files, and then use the real file as the message body.
> And then when its done it can delete/move both files.
> The problem is how to define an easy way of correlating the marker file to the real file. We can use an Expression for that.
> For example maybe something like, (use better option names)
> {{realFile=${file:name.noext}.csv&include=.*.ready}}
> Then Camel will react when there is a .ready file in the folder. And evaluate the expression and see if a file with that result exists.
> When it's done the marker file should be deleted, and the real file should be moved using the existing options for that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.