[jira] [Commented] (GEODE-5054) As a SDG user I want to be able to list and describe for my JDBC settings in gfsh

["John Blum (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GEODE-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446944#comment-16446944 ] 

John Blum commented on GEODE-5054:
----------------------------------

So, just a few questions here...

1) First, HOW do we envision "_Creating or updating JDBC mappings or connections_" WHEN using SDG?

2) Why do we think this? 

"_JDBC gfsh create, alter and destroy will work as expected in SDG, but not describe and list since they are only looking into CC for that information._"

That is...

2.1) That is, what do we mean "_Gfsh create, alter and destroy for JDBC will work as expected in SDG_?"

2.2) But then, "_not list and describe_"?

2.3) Is the thought that SDG does not honor/integrate with Cluster Config, because if this is the case, then we need to *stop* that misconception right now.  Also, I would ask, who thinks this?


> As a SDG user I want to be able to list and describe for my JDBC settings in gfsh
> ---------------------------------------------------------------------------------
>
>                 Key: GEODE-5054
>                 URL: https://issues.apache.org/jira/browse/GEODE-5054
>             Project: Geode
>          Issue Type: Bug
>          Components: extensions
>            Reporter: Fred Krone
>            Priority: Major
>              Labels: jdbc_connector
>
> GIVEN
> I am using SDG 
> WHEN
> Creating or updating JDBC mappings or connections
> THEN
> I should be able to list and describe these mappings or connections
>  
> Background
> JDBC gfsh create, alter and destroy will work as expected in SDG, but not describe and list since they are only looking into CC for that information. If we still want list and desc to work when cluster config service is disabled, can we require that the command would have a "--member" option, i.e. which member you want this information from.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)