[
https://issues.apache.org/jira/browse/IGNITE-14999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17501737#comment-17501737
]
Ignite TC Bot commented on IGNITE-14999:
----------------------------------------
{panel:title=Branch: [pull/9313/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/9313/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=6446358&buildTypeId=IgniteTests24Java8_RunAll]
> Support dynamic restoration of encrypted snapshots.
> ---------------------------------------------------
>
> Key: IGNITE-14999
> URL: https://issues.apache.org/jira/browse/IGNITE-14999
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Vladimir Steshin
> Assignee: Vladimir Steshin
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> After manual replacements of encrypted snapshots works, let's enable dynamic
> snapshot restoration (`SnapshotRestoreProcess`)
> Supposed new general features:
> * Dynamic restoration of encrypted snapshot on a running node (
> `IgniteSnapshotManager#restoreSnapshot()` )
> * Validation of encrypted snapshot ( `IgniteSnapshotManager#checkSnapshot()` )
> Same master key is still required.
> NOTE:
> To restore an encrypted snapshot, we have to read the keys it was encrypted
> with. The better place for the is Metastore. But it is currently unreadable
> as a simple structure. This ticket suggests holding the keys in
> `StoredCacheData`. It always goes together with the data and is included in
> snapshot.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
