ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1571) .Net: Improve Guid and DateTime reader/writer interface.
Date Fri, 09 Oct 2015 10:58:26 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950207#comment-14950207
] 

Pavel  Tupitsyn commented on IGNITE-1571:
-----------------------------------------

Agree to revert API changes since we keep specialized methods only for Java interoperability.
However, we can't throw exceptions when there is null for value type. This breaks a lot of
things. For example Cache<int, int>.Get() will throw an error if there is no such key,
which is incorrect.

> .Net: Improve Guid and DateTime reader/writer interface.
> --------------------------------------------------------
>
>                 Key: IGNITE-1571
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1571
>             Project: Ignite
>          Issue Type: Task
>          Components: interop
>    Affects Versions: ignite-1.4
>            Reporter: Vladimir Ozerov
>            Assignee: Pavel  Tupitsyn
>            Priority: Critical
>             Fix For: 1.5
>
>
> Currently we force user to write Guid and DateTime as nullables. We do this to be more
compatible with Java.
> But user is more likely to operate on plain types: Guid, Guid[], DateTime, DateTime[].

> We need to add these methods to API, and rename existing ones to "ReadNullableDateTime",
etc..
> Note that while trivial to on writer side, it will be harder to implement for readers.
Currently we lookup by type ID, which will be equal for the type and it's nullable counterpart.
For this reason we probably must lookup by type ID + type or simply by type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message