[
https://issues.apache.org/jira/browse/GEODE-4241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fred Krone updated GEODE-4241:
------------------------------
Description:
jdbc-mapping should be saved to cluster config but is lost when a server is
restarted.
A jdbc-connection is saved and is available when a server is restarted.
AC would be creating a jdbc-mapping, stopping and restarting the server..
Trying to recreate a jdbc-mapping with the same region should error because it
already exists.
Describing the jdbc-mapping should work after a restart.
was:
jdbc-mapping should be saved to cluster config but is lost when a server is
restarted.
A jdbc-connection is saved and is available when a server is restarted.
> jdbc-mapping is not stored in cluster configuration
> ---------------------------------------------------
>
> Key: GEODE-4241
> URL: https://issues.apache.org/jira/browse/GEODE-4241
> Project: Geode
> Issue Type: Bug
> Components: regions
> Reporter: Fred Krone
> Assignee: Anilkumar Gingade
> Fix For: 1.5.0
>
>
> jdbc-mapping should be saved to cluster config but is lost when a server is
> restarted.
> A jdbc-connection is saved and is available when a server is restarted.
> AC would be creating a jdbc-mapping, stopping and restarting the server..
> Trying to recreate a jdbc-mapping with the same region should error because
> it already exists.
> Describing the jdbc-mapping should work after a restart.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
