Skip to content

Enrich OSDU Data Storage in Ignite, Array Flatten and other issues

Levi Remington requested to merge 470_v2_EnrichFieldFlattening into master

Type of change

  • Bug Fix
  • Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)
#470 (closed)

Does this introduce a change in the core logic?

  • [YES/NO] YES

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a breaking change?

  • [YES/NO] NO

What is the current behavior?

Presently only 1 item of any property with array is stored.

What is the new/expected behavior?

  • Replace all property keys with . (dot) in name with _(underscore) for full compatibility with Ignite
  • Enhance merge definition to support properties with underscore.
  • If complex schema is encountered (array or object), the JSON value is stringified and stored
  • In special cases (Datasets, DDMSDatasets, , a delimited string is stored. In one other special case AvailableTrajectoryStationProperties a custom formatted string is stored using this pattern: type + ":" + unit + ":" + name

Have you added/updated Unit Tests and Integration Tests?

Any other useful information

Merge request reports