Details
-
Wish
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
Currently a ClientRegionShortcut.PROXY region sends operations like put() and get() over to the server, but for operations like size() and isEmpty() it just consults the local state on the client and returns 0 and true respectively, even though there may be data in the servers for that region.
A PROXY region should not attempt to consult its local state for any operation.
Attachments
Issue Links
1.
|
Add sizeOnServer and isEmptyOnServer to Region |
|
Closed | Eric Shu |
2.
|
Add containsKeyOnServer and containsValueOnServer to Region |
|
Open | Unassigned |
3.
|
Review getEntry on Region |
|
Open | Unassigned |
4.
|
Create on-server regions from the client |
|
Open | Unassigned |
5.
|
invalidateRegion on a CACHING_PROXY region throws NPE |
|
Open | Unassigned |
6.
|
Users need a default way to connect a client to an existing region on server |
|
Open | Darrel Schneider |