Align GemfireTemplate interface with Region interface [DATAGEODE-239]

[spring-projects-issues]

trafficstars

John Blum opened DATAGEODE-239 and commented

The o.s.d.g.GemfireTemplate class is missing several useful Region data access operations that should be present on the template:

• clear() - ?
• create(key, value, callbackArgument)
• destroy(key)
• destroy(key, callbackArgument)
• existsValue(queryPredicate)
• get(key, callbackArgument)
• getAll(keys, callbackArgument)
• getDistributedLock(key) - ?
• getEntry(key) - ?
• getRegionDistributedLock() - ?
• invalidate(key)
• invalidate(key, callbackArgument)
• isEmpty()
• isEmptyOnServer()
• keySet()
• keySetOnServer()
• localClear() - ?
• localDestroy(key) - ?
• localDestroy(key, callbackArgument) - ?
• localInvalidate(key) - ?
• localInvalidate(key, callbackArgument) - ?
• put(key, value, callbackArgument)
• putAll(map, callbackArgument)
• remove(key, callbackArgument)
• removeAll(keys)
• removeAll(keys, callbackArgument)
• selectValue(queryPredicate)
• size()
• sizeOnServer()

The question mark (?) is meant to indicate that the operation has limitations. For example, the Region operation may not be available for PRs or Distributed and Replicated Regions in general, or that a particular operations is specific only to a client or a peer/server.

The operation might throw a UnsupportedOperationException or IllegalStateException in certain cases.

The original intent of the GemfireTemplate was to encapsulate data access operations common to all Regions, regardless of data policy type or whether it was client or server

---

No further details from DATAGEODE-239