[
https://issues.apache.org/jira/browse/GEODE-6291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16774656#comment-16774656
]
ASF subversion and git services commented on GEODE-6291:
--------------------------------------------------------
Commit e762da8c66a5cbd13ea3a5e4728ca6cf6cb2c53d in geode's branch
refs/heads/develop from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e762da8 ]
GEODE-6291: change create mapping to define column and pdx field information
(#3155)
Create mapping now requires that the pdx class exists on the server.
It generates a FieldMapping definition for each column/field. It will load the
pdx class and
generate a pdx type for it, failing if it can not do so.
If the pdx type field count does not match the table column count then it will
fail.
The pdx field names can differ in case from the column names as long as only
one field matches the column.
Authored-by: Benjamin Ross <[email protected]>
Authored-by: Darrel Schneider <[email protected]>
> 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
> 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)
