[
https://issues.apache.org/jira/browse/GEODE-5935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16670260#comment-16670260
]
ASF subversion and git services commented on GEODE-5935:
--------------------------------------------------------
Commit 04c1d0ed2f569e33a99a5109bba432ad9f8a7c33 in geode's branch
refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=04c1d0e ]
GEODE-5935: move jdbc xml mapping to be in a region (#2739)
The jdbc region-mapping xml element is now jdbc:mapping.
It no longer has a "region" attribute since it is nested in a region.
Creating a jdbc-mapping requires that the region already exists.
The jdbc:mapping element is now nested in a region element instead of the cache
element.
The old connector-service element has been completely removed.
Some of the jdbc-mapping gfsh commands now require at least one server to be
running.
Co-authored-by: Darrel Schneider <[email protected]>
Co-authored-by: Jianxia Chen <[email protected]>
Co-authored-by: Ben Ross @BenjaminPerryRoss
> jdbc connector xml mapping should be at the region level instead of cache
> level
> -------------------------------------------------------------------------------
>
> Key: GEODE-5935
> URL: https://issues.apache.org/jira/browse/GEODE-5935
> 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
>
> The jdbc connector xsd defines the jdbc mapping at the cache level.
> It should instead have it at the region level since each jdbc mapping if for
> a specific region.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
