[
https://issues.apache.org/jira/browse/IGNITE-25496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18108912#comment-18108912
]
Ignite TC Bot commented on IGNITE-25496:
----------------------------------------
I reviewed implementation PR #12100 and commit f9fb5c7deb in the local Ignite 2
checkout. This fixes snapshot restore for non-serializable cache group name
collections by copying the existing input collection internally; it does not
change the public snapshot restore API or documentation contract. I removed
only Docs Required and preserved Release Notes Required.
> SnapshotRestoreProcess#restoreSnapshot fails if cacheGroupNames collection is
> not Serializable
> ----------------------------------------------------------------------------------------------
>
> Key: IGNITE-25496
> URL: https://issues.apache.org/jira/browse/IGNITE-25496
> Project: Ignite
> Issue Type: Task
> Reporter: Vladislav Novikov
> Assignee: Vladislav Novikov
> Priority: Major
> Labels: ise
> Fix For: 2.18
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When calling the {{restoreSnapshot(String name, @Nullable Collection<String>
> cacheGroupNames)}} method with a non-serializable collection (e.g.
> {{{}HashMap.keySet(){}}}), the operation fails with
> {{{}NotSerializableException{}}}.
> This happens because the collection is being serialized during internal
> communication via discovery SPI, but the method's contract does not
> explicitly require the collection to be serializable. As a result, users may
> pass valid {{Collection<String>}} implementations that are not
> {{{}Serializable{}}}, leading to unexpected runtime errors.
> Expected behavior: the method accepts any {{Collection<String>}} and
> internally handles serialization safely.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
