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 2018/12/19 17:45:00 UTC
[jira] [Commented] (GEODE-6194) create jdbc-mapping --id should
support multiple columns
[ https://issues.apache.org/jira/browse/GEODE-6194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725214#comment-16725214 ]
ASF subversion and git services commented on GEODE-6194:
--------------------------------------------------------
Commit bd9c284975bfb0b8caef15ab6205af972d76cf41 in geode's branch refs/heads/develop from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=bd9c284 ]
GEODE-6194: add composite keys to jdbc (#3015)
Multiple --id column names can now be specified on "create jdbc-mapping"
using a comma separated list.
The key object itself must then be a JSON string whose names are
the corresponding pdx field name for each id column name.
The extension team is looking into changing composite keys for both GGC and JDBC
to something other than JSON.
> create jdbc-mapping --id should support multiple columns
> --------------------------------------------------------
>
> Key: GEODE-6194
> URL: https://issues.apache.org/jira/browse/GEODE-6194
> Project: Geode
> Issue Type: Improvement
> Components: extensions
> Reporter: Darrel Schneider
> Assignee: Darrel Schneider
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> *As a* Geode user
> *I want to* be able to specify more than one column in a JDBC table for the --id option
> *so that I can* support a composite key for the Geode region and match behavior of GGC.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)