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

Posted to issues@geode.apache.org by "Anilkumar Gingade (JIRA)" <ji...@apache.org> on 2018/03/08 20:40:00 UTC

[jira] [Updated] (GEODE-4693) JDBCLoader on region with a pdx-class-name causes exception during deserialization when a get is done

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

Anilkumar Gingade updated GEODE-4693:
-------------------------------------
    Component/s: docs

> JDBCLoader on region with a pdx-class-name causes exception during deserialization when a get is done
> -----------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-4693
>                 URL: https://issues.apache.org/jira/browse/GEODE-4693
>             Project: Geode
>          Issue Type: Bug
>          Components: docs, extensions, regions
>    Affects Versions: 1.4.0
>            Reporter: Fred Krone
>            Assignee: Anilkumar Gingade
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When Region.get() is performed with JDBCLoader and pdx-class-name, the JDBCLoader always creates a PdxInstance whose fields are all of type object. If the domain class has the fields as some other type, for example string or int, then deserialization will fail.
> Workaround at this time is:
>  # Don't set the pdx-class-name on the jdbc region mapping. This will cause deserialization to never happen since the data will remain a PdxInstance.
>  #  Have all your domain class fields serialized as pdx object fields. This can be hard to do with the ReflectionBasedAutoSerializer so the recommendation is to use PdxSerializable or your own PdxSerializer.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)