You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Juan José Ramos Cassella (JIRA)" <ji...@apache.org> on 2017/12/07 11:18:00 UTC
[jira] [Resolved] (GEODE-878) Cannot specify PartitionResolver
through gfsh
[ https://issues.apache.org/jira/browse/GEODE-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juan José Ramos Cassella resolved GEODE-878.
--------------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0
Fixed by 95ad1643874cd37d8c3b9dbcae8923ea58fe5be7.
> Cannot specify PartitionResolver through gfsh
> ---------------------------------------------
>
> Key: GEODE-878
> URL: https://issues.apache.org/jira/browse/GEODE-878
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Reporter: Swapnil Bawaskar
> Fix For: 1.1.0
>
>
> 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.4.14#64029)