ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amelchev Nikita (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-6135) java.sql.Date is serialized using OptimizedMarshaller
Date Tue, 10 Oct 2017 17:52:06 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Amelchev Nikita reassigned IGNITE-6135:
---------------------------------------

    Assignee: Amelchev Nikita

> java.sql.Date is serialized using OptimizedMarshaller
> -----------------------------------------------------
>
>                 Key: IGNITE-6135
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6135
>             Project: Ignite
>          Issue Type: Bug
>          Components: binary
>    Affects Versions: 2.1
>            Reporter: Valentin Kulichenko
>            Assignee: Amelchev Nikita
>
> For some reason, if an object has a field of {{java.sql.Date}}, it's serialized with
{{OptimizedMarshaller}}. It should be a first class citizen, similar to {{java.util.Date}}.
> In addition, it's possible to write a field using builder like this:
> {code}
> builder.setField(name, val, java.util.Date.class)
> {code}
> where {{val}} is instance of {{java.sql.Date}}. This leads to an exception during deserialization,
because {{java.util.Date}} would be expected.
> More context and code reproducing the issue can be found here: http://apache-ignite-users.70518.x6.nabble.com/JDBC-store-Date-deserialization-problem-td16276.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message