You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2016/08/18 16:37:20 UTC
[jira] [Resolved] (IGNITE-3696) .NET: Java type mapping does not
work with nullable types
[ https://issues.apache.org/jira/browse/IGNITE-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn resolved IGNITE-3696.
------------------------------------
Resolution: Fixed
> .NET: Java type mapping does not work with nullable types
> ---------------------------------------------------------
>
> Key: IGNITE-3696
> URL: https://issues.apache.org/jira/browse/IGNITE-3696
> Project: Ignite
> Issue Type: Bug
> Components: platforms
> Affects Versions: 1.6
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Minor
> Labels: .net
> Fix For: 1.8
>
>
> See JavaTypes class. We should probably map nullables there too.
> Java has everything nullable by default, need to explain to the users that anything can be null underneath.
> Make sure to test this with [QuerySqlField].
> Workaround is to use manual QueryEntity configuration and specify either non-nullable .NET type, or the Java type name.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)