[
https://issues.apache.org/jira/browse/IGNITE-16042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksandr Polovtcev updated IGNITE-16042:
-----------------------------------------
Description:
Given the following situation:
# There exists a {{NamedList x = ["foo" -> "bar", "baz" -> "quux"]}}
# Execute something like the following {{x.change(c ->
c.delete("foo").insertAfter("foo", ...))}}. I.e. we are calling {{insertAfter}}
on a key that has been deleted in the same change closure.
Currently this code works without errors (effectively inserting a key before
{{baz}}), which is inconsistent with all other methods of this class that will
throw an exception instead. It is proposed to make this method fail as well
> NamedListChange#createAfter should fail if called on a deleted key
> ------------------------------------------------------------------
>
> Key: IGNITE-16042
> URL: https://issues.apache.org/jira/browse/IGNITE-16042
> Project: Ignite
> Issue Type: Task
> Reporter: Aleksandr Polovtcev
> Assignee: Aleksandr Polovtcev
> Priority: Minor
> Labels: ignite-3
>
> Given the following situation:
> # There exists a {{NamedList x = ["foo" -> "bar", "baz" -> "quux"]}}
> # Execute something like the following {{x.change(c ->
> c.delete("foo").insertAfter("foo", ...))}}. I.e. we are calling
> {{insertAfter}} on a key that has been deleted in the same change closure.
> Currently this code works without errors (effectively inserting a key before
> {{baz}}), which is inconsistent with all other methods of this class that
> will throw an exception instead. It is proposed to make this method fail as
> well
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
