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] [Resolved] (IGNITE-3308) IGFS: Introduce separate processor for "move" operation when parent is the same for source and destination.
Date Tue, 14 Jun 2016 09:39:01 GMT

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

Vladimir Ozerov resolved IGNITE-3308.
-------------------------------------
    Resolution: Fixed

> IGFS: Introduce separate processor for "move" operation when parent is the same for source
and destination.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-3308
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3308
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: IGFS
>    Affects Versions: 1.6
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>             Fix For: 1.7
>
>
> Consider the following operation: {{move("/parent/a", "parent/b")}}.
> In this case we will call two entry processors: {{IgfsMetaDirectoryListingRemoveProcessor}}
to unlink "a" and {{IgfsMetaDirectoryListingAddProcessor}} to link "b". 
> Instead, we should call only a single processor as source and destination keys are the
same. This will save network traffic and possibly decrease number of remote calls.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message