You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Barbara Pruijn (JIRA)" <ji...@apache.org> on 2018/02/20 17:48:02 UTC
[jira] [Resolved] (GEODE-4626) deprecating create region using
--template-region option in gfsh
[ https://issues.apache.org/jira/browse/GEODE-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barbara Pruijn resolved GEODE-4626.
-----------------------------------
Resolution: Fixed
> deprecating create region using --template-region option in gfsh
> ----------------------------------------------------------------
>
> Key: GEODE-4626
> URL: https://issues.apache.org/jira/browse/GEODE-4626
> Project: Geode
> Issue Type: Improvement
> Components: docs, gfsh
> Affects Versions: 1.4.0
> Reporter: Jinmei Liao
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> currently, there are two ways to create a region, either to use a --type option indicating a region shortcut or a --template-region option specifying another regionPath where you want to copy the attribute from.
> First of all, we are not sure what set of attributes that make sense to copy to the new region. e.g listeners/loaders/writers, normally these are connected to a downstream database that user may/may not want the new region to read/write the same table. And the current implementation would fail to create a region from a template that has these custom callbacks (including listeners, loader, writer, compressor, resolvers etc).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)