[
https://issues.apache.org/jira/browse/IGNITE-22001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-22001:
-------------------------------------
Fix Version/s: 3.0.0-beta2
> Throw specific exception if during writeTableAssignmentsToMetastore process
> was interrupted
> -------------------------------------------------------------------------------------------
>
> Key: IGNITE-22001
> URL: https://issues.apache.org/jira/browse/IGNITE-22001
> Project: Ignite
> Issue Type: Improvement
> Reporter: Mikhail Efremov
> Assignee: Mikhail Efremov
> Priority: Minor
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> h2. The problem
> In {{TableManager#writeTableAssignmentsToMetastore:752}} as a result of
> output {{CompletableFuture}} returns {{{}null{}}}-value. In cases of
> {{writeTableAssignmentsToMetastore}} method's using it leads to sudden
> {{NullPointerException}} without clear understandings of the reasons of such
> situation.
> h2. The solution
> Instead of returning {{{}null{}}}-value re-throw more specific exception with
> given assignments list to write in metastorage, and table identifier that
> should help to investigate cases of the method interruption.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
