[
https://issues.apache.org/jira/browse/GEODE-6365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772522#comment-16772522
]
ASF subversion and git services commented on GEODE-6365:
--------------------------------------------------------
Commit 49696f83c70606673758a19cf904b544d1df4346 in geode's branch
refs/heads/feature/GEODE-6291 from BenjaminPerryRoss
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=49696f8 ]
GEODE-6365: Group support for JDBC mapping logic in DestroyRegionCommand (#3202)
Added server group support for the logic in destroy region which
checks for an existing jdbc-mapping
> Add server group support for JDBC List Mapping and Destroy Mapping Commands
> ---------------------------------------------------------------------------
>
> Key: GEODE-6365
> URL: https://issues.apache.org/jira/browse/GEODE-6365
> Project: Geode
> Issue Type: Improvement
> Reporter: Benjamin P Ross
> Assignee: Benjamin P Ross
> Priority: Major
> Labels: pull-request-available
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> As a Geode user, I want to specify which server group holds the region, so
> that I can add the JDBC mapping to that region.
> Given a jdbc-mapping exists for a Geode region on a server group, when I run
> list jdbc-mapping for that region
> Then I can specify the server group with an option on the command line, so
> that the jdbc-mappings displayed are limited to the mappings in the specified
> server group.
> Given a jdbc-mapping exists for a Geode region on a server group, when I run
> destroy jdbc-mapping for that region
> Then I can specify the server group with an option on the command line, so
> that the jdbc-mapping will only be destroyed if it is found in the specified
> group.
> This is a follow up to the story:
> https://issues.apache.org/jira/browse/GEODE-6273
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
