You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/02 01:16:01 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16758807#comment-16758807 ]
ASF subversion and git services commented on GEODE-6291:
--------------------------------------------------------
Commit 726129d4adf7650f7f5d69b747ff92b920af1ad0 in geode's branch refs/heads/feature/GEODE-6291 from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=726129d ]
Merge remote-tracking branch 'origin/develop' into feature/GEODE-6291
> 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
>
> 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)