[jira] Created: (CAMEL-909) file component - timestamp option to enable/disable the last poll timestamp

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (CAMEL-909) file component - timestamp option to enable/disable the last poll timestamp

JIRA jira@apache.org
file component - timestamp option to enable/disable the last poll timestamp
---------------------------------------------------------------------------

                 Key: CAMEL-909
                 URL: https://issues.apache.org/activemq/browse/CAMEL-909
             Project: Apache Camel
          Issue Type: Improvement
          Components: camel-core
    Affects Versions: 1.4.0
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
             Fix For: 1.5.0


camel-ftp now has the option consumer.timestamp to disable/enable using timestamp check for new files.

The regular file component should also has this option. Then there is no surprises for end-users. This will allow then to copy files into the folder preserving original timestamp etc.
We should consider disabling this by default as its better to use another strategy for detecting new files, such as
- deleting consumed files
- moving consumed files (does this by default)



--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Work started: (CAMEL-909) file component - timestamp option to enable/disable the last poll timestamp

JIRA jira@apache.org

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

Work on CAMEL-909 started by Claus Ibsen.

> file component - timestamp option to enable/disable the last poll timestamp
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-909
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-909
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 1.5.0
>
>
> camel-ftp now has the option consumer.timestamp to disable/enable using timestamp check for new files.
> The regular file component should also has this option. Then there is no surprises for end-users. This will allow then to copy files into the folder preserving original timestamp etc.
> We should consider disabling this by default as its better to use another strategy for detecting new files, such as
> - deleting consumed files
> - moving consumed files (does this by default)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (CAMEL-909) file component - timestamp option to enable/disable the last poll timestamp

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/activemq/browse/CAMEL-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45739#action_45739 ]

Claus Ibsen commented on CAMEL-909:
-----------------------------------

We actually already have the option *consumer.alwaysConsume* for this.
So I am adding *consumer.timestamp* to let the file and ftp component have same options in this regards. And also adding the wiki warning.

I have marked the code in the file component that computes if a file is changed or not. The code is to messy and we don't want to compute if a file is changed if the file size is different etc. It keeps an internal state of processed files and its lost when you restart Camel. So its should be removed.

End-users should do the same as the ftp. Files to be consumed from a folder should be moved/delete after processing. So new files is not hard to compute = there is a file in the folder.

> file component - timestamp option to enable/disable the last poll timestamp
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-909
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-909
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 1.5.0
>
>
> camel-ftp now has the option consumer.timestamp to disable/enable using timestamp check for new files.
> The regular file component should also has this option. Then there is no surprises for end-users. This will allow then to copy files into the folder preserving original timestamp etc.
> We should consider disabling this by default as its better to use another strategy for detecting new files, such as
> - deleting consumed files
> - moving consumed files (does this by default)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (CAMEL-909) file component - timestamp option to enable/disable the last poll timestamp

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Claus Ibsen resolved CAMEL-909.
-------------------------------

    Resolution: Fixed

> file component - timestamp option to enable/disable the last poll timestamp
> ---------------------------------------------------------------------------
>
>                 Key: CAMEL-909
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-909
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 1.5.0
>
>
> camel-ftp now has the option consumer.timestamp to disable/enable using timestamp check for new files.
> The regular file component should also has this option. Then there is no surprises for end-users. This will allow then to copy files into the folder preserving original timestamp etc.
> We should consider disabling this by default as its better to use another strategy for detecting new files, such as
> - deleting consumed files
> - moving consumed files (does this by default)

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.