[
https://issues.apache.org/jira/browse/GEODE-2885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999044#comment-15999044
]
Fred Krone commented on GEODE-2885:
-----------------------------------
Current local/client only Region methods
-- should "onServer" methods be added for these?
RegionAttributes<K, V> getAttributes();
-- no: should always be local attributes
AttributesMutator<K, V> getAttributesMutator();
-- no: should always be local attributes mutator
CacheStatistics getStatistics();
-- no: should be local
Entry<K, V> getEntry(Object key);
maybe
Region<SK, SV> getSubregion(String path);
no: should always be subregion in the local cache
Set<Region<?, ?>> subregions(boolean recursive);
no: should always be subregions that exist in the local cache
public Set<K> keySet();
yes: already implemented as keySetOnServer
Collection<V> values();
maybe
Set<Region.Entry<?, ?>> entrySet(boolean recursive);
maybe
Set<Map.Entry<K, V>> entrySet();
maybe
Object getUserAttribute();
no: should always be local
void setUserAttribute(Object value);
no: should always be local
boolean isDestroyed();
no: should always be local
containsValueForKey(Object key);
should be same as getEntry
boolean containsKey(Object key);
should be same as getEntry: already implemented as containsKeyOnServer
boolean containsValue(Object value);
maybe
boolean isEmpty();
yes: same as size
int size();
yes
void forEach(BiConsumer<? super K, ? super V> action)
same as entrySet
void replaceAll(BiFunction<? super K, ? super V, ? extends V> function)
same as entrySet
> Client users need an easy way to check on server
> ------------------------------------------------
>
> Key: GEODE-2885
> URL: https://issues.apache.org/jira/browse/GEODE-2885
> Project: Geode
> Issue Type: Improvement
> Components: regions
> Reporter: Fred Krone
>
> When "getting" a region from the client, and putting or getting to that
> region, certain methods can be very confusing.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
