[jira] [Commented] (GEODE-3824) Paramaterize CacheWriter, CacheLoader via GFSH

["Darrel Schneider (JIRA)" <ji...@apache.org>]

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

Darrel Schneider commented on GEODE-3824:
-----------------------------------------

In general, anytime gfsh accepts a class name it should also support parameters. One way of doing this is to have the customer that implemented the class to also implement the Declarable interface. The cluster configuration parser current requires this. I think supporting the Declarable interface from gfsh for all class names is the bare minimum of what we need to support.
Having a separate gfsh command option for the parameters is okay but kind of verbose. I would prefer something like this:
--cache-writer=MyCacheWriter(key1, value1, key2, value2)
over this:
--cache-writer=MyCacheWriter --cache-writer-parameters=key1,value1,key2,value2
but I could be wrong. The cache-writer-parameters is auto completable

> Paramaterize CacheWriter, CacheLoader via GFSH
> ----------------------------------------------
>
>                 Key: GEODE-3824
>                 URL: https://issues.apache.org/jira/browse/GEODE-3824
>             Project: Geode
>          Issue Type: Sub-task
>          Components: gfsh
>            Reporter: Fred Krone
>
> Need to be able to add new properties to CacheWriter or CacheLoader through GFSH.
> The gfsh creation region command needs to support this.
> The gfsh alter region commands needs to support this.
> The gfsh create async-event-queue has support for this with its --listener-param option.
> Need a way for the user to add the JDBC url and credentials to be called on DB connection.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)