[
https://issues.apache.org/jira/browse/CONNECTORS-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16624497#comment-16624497
]
James Thomas commented on CONNECTORS-1534:
------------------------------------------
{quote}For backwards compatibility reasons, you'd therefore want to add
specification information to the connector describing how you want deletions to
be handled, which is basically a significant enhancement to the connector, so I
would ask if this is really something you need or just something you don't like.
{quote}
I find it (very) unexpected but it's not breaking anything for me.
Given what I know, I think that from the consumer of the FS connector's output
it's (at best) ambiguous whether the file originated at zero size or existed
and was then deleted. This may make a difference in some applications.
At the moment – as you know :) – I'm primiarly working with the Documentum
repository connector and it won't fetch zero size files
(https://issues.apache.org/jira/browse/CONNECTORS-1526) so I don't have the
ambiguity. I'm also only really using the FS connector as a tool for testing so
far.
> File System connector "deletes" files by making them zero bytes
> ---------------------------------------------------------------
>
> Key: CONNECTORS-1534
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1534
> Project: ManifoldCF
> Issue Type: Bug
> Components: File system connector
> Affects Versions: ManifoldCF 2.10
> Reporter: James Thomas
> Assignee: Karl Wright
> Priority: Major
> Fix For: ManifoldCF next
>
>
> In https://issues.apache.org/jira/browse/CONNECTORS-1532 I observed that
> deleting a file from a repository does not (reliably?) delete it from a File
> System output. Instead the output file remains but is given zero size and a
> new modification time.
> I would expect that a file deletion in the repository results in file
> deletion in the output.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
