Page History

...

https://cwiki.apache.org/confluence/display/GEODE/Proposal+for+pluggable+cache+stores

Open Questions on requirements & scope

• Should multiple cache stores per region be a goal? If yes, the following question naturally come up:
  • Should write-only cache stores be supported (use case- write data for batch analytics)?
  • Only one recovery store can be used when Geode needs to initialize a region- should this be decided by a priority list (order of trying read/write stores to recover)?
• Data filters- should data filters be supported for write?
• How exactly is transition handled for distributed cache store case; possibility- maintain a last N entries queue and seed the async write queue with this during transition. Corner cases here a concern- loss of events is primary concern. 
• Can cache stores be added during region operation or only at start/restart?
• Scan with filter support in initial implementation?
• OQL support in initial cut?
• Adding new cache stores types/purposes may require behavior on cache store unavailable (write fail or get fail) to be configurable, should such configuration be supported?
• Should data event change register be supported for cache stores that support generating such notifications?
• Should pluggable cache stores be usable for overflow or limited to data persistence and export (if write-only supported)?