You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Sai Boorlagadda (JIRA)" <ji...@apache.org> on 2019/03/25 16:23:03 UTC

[jira] [Updated] (GEODE-6291) gfsh create jdbc-mapping should store pdx field to JDBC table column mapping to cluster config

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

Sai Boorlagadda updated GEODE-6291:
-----------------------------------
    Fix Version/s:     (was: 1.10.0)
                   1.9.0

> gfsh create jdbc-mapping should store pdx field to JDBC table column mapping to cluster config
> ----------------------------------------------------------------------------------------------
>
>                 Key: GEODE-6291
>                 URL: https://issues.apache.org/jira/browse/GEODE-6291
>             Project: Geode
>          Issue Type: Improvement
>          Components: extensions
>    Affects Versions: 1.9.0
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>            Priority: Major
>             Fix For: 1.9.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Currently 'gfsh create jdbc-mapping' does not define any of the actual pdx field to column mapping information. Instead it just waits until a get or put is done and then figures out how to do the mapping.
> gfsh create jdbc-mapping should instead read the meta data from the table and figure out how to map the columns to pdx. The mapping it determines should be stored in cluster config.
>  



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