ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1679) IGFS: Purge event is inconsistent.
Date Tue, 22 Mar 2016 08:10:25 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205978#comment-15205978

Vladimir Ozerov commented on IGNITE-1679:


Please see linked ticket. In order to track path of removed file we relied on {{IgfsEntryInfo.path}}
field which was updated by a special entry processor. This is less than optimal solution.
Instead, we should do the following:
1) When any entry is moved to trash, it's name in trash listing must be unique, but still
has original path name. E.g., it could be encoded as "path|id". This way we will always know
entry origin, while still maintaining unique name in trash listing.
2) As we removed entries in delete worked, we constantly track current path. When file is
purged finally, we fire and event with the path.

Please do not forget to add tests for this (just revert changes to {{IgfsEventsAbstractSelfTest}}
performed in scope of IGNITE-2871).

> IGFS: Purge event is inconsistent.
> ----------------------------------
>                 Key: IGNITE-1679
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1679
>             Project: Ignite
>          Issue Type: Bug
>          Components: hadoop
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>             Fix For: 1.6
> Currently PURGE event is fired only to files which were deleted explicitly. It is not
fired which are deleted as a part of recursive deletion of parent directory.
> To fix that we should set the last known entry path when moving it to trash. This way
we will be able to calculate path for each removed child entry.
> Another question is do we really need to fire events for child entries. Or we should
only fire them for the target entries.

This message was sent by Atlassian JIRA

View raw message