Skip to content

Implement connect to existing cache logic

Levi Remington requested to merge transformer-spring-refactor-existing-cache-lr into transformer-spring-refactor-pad
  • When running Transformer with 'remote' profile, Default Feature Cache will connect to existing Ignite Cluster on application.host
  • If cache cannot be found, a cache will be created and populated
  • If cache is found, default behavior is to connect only (no populating/updating)
  • updateCache() function can be used to destroy/init/populate a cache (future plan: call this from scheduler)
  • Moved identical shared functions (initCache, putFeatures, generateFieldDefinitions, getFieldValueType, configureQueryEntity) from DefaultFeatureCache/OnDemandFeatureCache up to AbstractFeatureCache
  • Added clarity to some logs ("put x features into cache" now states the cache/kind)
  • Merged kind/cache functionality and replicated for DefaultFeatureCache/FeatureCacheSynchronizer
  • Update Transformer and Provider ReadMes
Edited by Levi Remington

Merge request reports