# HydraCache Java migration Hazelcast API manifest.
# Format: version=N, then supported|API|migration hint or unsupported|API|migration hint.
version=2
supported|IMap.lock|Use HydraFencedLock as a single-key linearizable fenced lock; pass the returned fence to your system of record. Not cross-region linearizable and not reentrant across processes unless the same session identity is supplied.
supported|IMap.tryLock|Use HydraFencedLock.tryLock as a protocol-v2 TryLock mapping; pass the returned fence to your system of record. Timed waits are client-side retry loops over the same single-key lock.
supported|IMap.replace|Use HydraCacheMap.replace as a protocol-v2 CompareAndSet mapping. Exact old-value replace and replace-if-present are distinct expectation modes; absent keys mismatch.
supported|IMap.remove(key,value)|Use HydraCacheMap.remove_if as a protocol-v2 RemoveIfValue mapping. A match writes a versioned tombstone; mismatch returns the current value.
supported|IMap.addEntryListener|Use HydraCacheMap.addEntryListener as a protocol-v2 SubscribeEntryEvents mapping. It is a bounded/coalesced cache signal, not a business event log; includeValue is best-effort and residency-gated.
supported|FencedLock|Use HydraFencedLock for the lock-by-key subset. ForceUnlock is privileged, audited, and fence-advancing; this is source-level ergonomics, not Hazelcast wire compatibility.
supported|HazelcastInstance.getCPSubsystem().getLock|Lock-only CP migration path: use HydraFencedLock. Other CP structures remain unsupported.
unsupported|HazelcastInstance.getExecutorService|HydraCache does not run server-side application code; keep execution in the application JVM or job system.
unsupported|HazelcastInstance.getSql|HydraCache does not provide Hazelcast SQL; query the source database/search system and cache explicit results.
unsupported|IMap.executeOnKey|Entry processors execute code inside Hazelcast members; move logic to application services and write explicit cache updates/invalidations.
unsupported|IMap.addInterceptor|Server-side map interceptors are unsupported; use application-side decorators around HydraCacheMap.
unsupported|ReplicatedMap|HydraCache exposes cache namespaces and replication policy, not Hazelcast ReplicatedMap semantics; model data as a cache map or source-of-truth table.
unsupported|Ringbuffer|HydraCache invalidation streams are for near-cache repair, not a general event log; use Kafka/outbox for business events.
unsupported|ReliableTopic|HydraCache invalidation subscriptions are cache signals, not general pub/sub; use an event bus for business messages.
unsupported|PNCounter|HydraCache does not expose Hazelcast CRDT objects through the Java migration facade; use source-of-truth writes or a dedicated counter service.
