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

Swapnil Bawaskar commented on GEODE-878:
----------------------------------------

Also see GEODE-881.

> Cannot specify PartitionResolver through gfsh
> ---------------------------------------------
>
>                 Key: GEODE-878
>                 URL: https://issues.apache.org/jira/browse/GEODE-878
>             Project: Geode
>          Issue Type: Bug
>          Components: management
>            Reporter: Swapnil Bawaskar
>
> When trying to create a Partitioned Region using gfsh, users should be able 
> to specify the PartitionResolver class used by that region. The current 
> options are: 
> {code}
> gfsh>create region --name=foo --type=PARTITION --
>  --template-region                          --group                           
>          --skip-if-exists                           --async-event-queue-id
>  --cache-listener                           --cache-loader                    
>          --cache-writer                             --colocated-with
>  --compressor                               --concurrency-level               
>          --disk-store                               --enable-async-conflation
>  --enable-cloning                           --enable-concurrency-checks       
>          --enable-multicast                         --enable-statistics
>  --enable-subscription-conflation           --enable-synchronous-disk         
>          --entry-idle-time-expiration               
> --entry-idle-time-expiration-action
>  --entry-time-to-live-expiration            
> --entry-time-to-live-expiration-action     --gateway-sender-id                
>         --key-constraint
>  --local-max-memory                         --off-heap                        
>          --region-idle-time-expiration              
> --region-idle-time-expiration-action
>  --region-time-to-live-expiration           
> --region-time-to-live-expiration-action    --recovery-delay                   
>         --redundant-copies
>  --startup-recovery-delay                   --total-max-memory                
>          --total-num-buckets                        --value-constraint
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to