Transformer: Track FieldDefinitions per-cache in a separate Key to share column metadata with Provider
As a GCZ Developer, I would like for the GCZ Provider (Node.js Apache Ignite Thin Client) to be able to interrogate with an Ignite Cache and identify all available fields. Current Ignite API does not allow for this. This limitation makes it difficult for users to configure koop-config.json because the process of configuring fields is of trial-and-error.
Acceptance Criteria:
- Transformer writes to the "definitions" key of an Ignite Cache upon initialization, storing a simple comma-separated string of field names.
- GCZ Provider confirms it can access said "definitions" key by calling
cache.get('definitions')
Future issue: Use definitions metadata to gracefully construct dynamic queries.