[
https://issues.apache.org/jira/browse/GEODE-4626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jinmei Liao updated GEODE-4626:
-------------------------------
Description:
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).
was:
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).
> 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: gfsh
> Affects Versions: 1.4.0
> Reporter: Jinmei Liao
> Priority: Major
>
> 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)
