Skip to content

Refactor Koop to connect to multiple caches depending on config

Levi Remington requested to merge refactor-koop-multiple-caches-lr into transformer-spring-refactor-pad
  • ignite-provider default.json config now supports layer number, ignite schema, and ignite table properties
    • These properties are used to determine which Ignite Cache to connect to for any given query
    • Example: FeatureServer/1/query will connect to Well cache, whereas FeatureServer/3/query will connect to Seismic cache
  • Transformer was updated to store geometryType per record. After the recent refactor, geometryType was getting set to "Feature" when previously it was set to the geometry type (Point, Polygon, LineString, etc.)
    • This piece is crucial for Koop to query our Seismic cache, as that cache has multiple geometry types and Koop should only be producing a single feature layer per geometry type
  • Tested and confirmed: Koop can now produce feature layers from all of our caches
  • Fixed bug where you could not plug a Koop produced (and ngrok'd) feature layer URL into Portal
  • Koop code has been reduced and streamlined, and the containing directory has been named "osdu_gcz_provider"

Resolves issue #126 (closed)

Merge request reports