[
https://issues.apache.org/jira/browse/IGNITE-9736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16631660#comment-16631660
]
Andrew Mashenkov commented on IGNITE-9736:
------------------------------------------
[~Jokser],
# Please, share your thoughts on dev list related to listener
deprecation\removal or making private.
# Your change will force user to return smth from this method.
Is it hard to just wrap internal future into public one?
Is it ok if null will be returned by user or non-null future is mandatory?
Let's fix javadoc if so, otherwise it should be adapt to public IgniteFuture.
Code freeze is coming and we need a solution.
> Public interface DiscoverySpiListener.onDiscovery returns private API class
> ---------------------------------------------------------------------------
>
> Key: IGNITE-9736
> URL: https://issues.apache.org/jira/browse/IGNITE-9736
> Project: Ignite
> Issue Type: Bug
> Components: general
> Reporter: Andrew Mashenkov
> Priority: Critical
> Fix For: 2.7
>
>
> Public interface DiscoverySpiListener.onDiscovery returns
> IgniteInternalFuture of 'internal' package.
> We should wrap internal future into IgniteFuture of public API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
