You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2021/10/25 09:40:00 UTC

[jira] [Commented] (IGNITE-15067) Add custom destination path to the snapshost API

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

Pavel Pereslegin commented on IGNITE-15067:
-------------------------------------------

Perhaps it makes sense to add such a feature when restoring a snapshot too (without workdir restriction). 

This will simplify restoring to another cluster from an external resource (mounted to the server).

> Add custom destination path to the snapshost API
> ------------------------------------------------
>
>                 Key: IGNITE-15067
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15067
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Maxim Muzafarov
>            Assignee: Maxim Muzafarov
>            Priority: Major
>              Labels: iep-43
>             Fix For: 2.12
>
>
> The default configuration path obtains from the IgniteConfiguration. However, in some circumstances, it is good to set this destination path at runtime. This path must be configured relatively in the node working directory and must be accessible from the security point of view.
> Proposed API:
> {code}
>     public IgniteFuture<Void> createSnapshot(String name, Path locPath);
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)