You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Yashasvi Kotamraju (JIRA)" <ji...@apache.org> on 2017/09/27 05:40:00 UTC

[jira] [Updated] (IGNITE-6500) While using ignite-cassandra-store, POJO field having wrapper type, mapped to Cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null.

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

Yashasvi Kotamraju updated IGNITE-6500:
---------------------------------------
    Affects Version/s: 2.1
        Fix Version/s: 2.3

> While using ignite-cassandra-store, POJO field having wrapper type, mapped to Cassandra table are getting initialized to respective default value of primitive type instead of null if column value is null. 
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-6500
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6500
>             Project: Ignite
>          Issue Type: Bug
>          Components: cassandra
>    Affects Versions: 2.1
>            Reporter: Yashasvi Kotamraju
>            Assignee: Yashasvi Kotamraju
>            Priority: Minor
>             Fix For: 2.3
>
>
> While using  ignite-cassandra-store, if a POJO field is of wrapper class type, and the column value mapped in cassandra persistent store is null then the POJO field is getting set to default primitive type instead of null.



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