... | ... | @@ -172,7 +172,7 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha |
|
|
- Fetch query does not respect [wildcard syntax](https://community.opengroup.org/osdu/platform/data-flow/ingestion/external-data-sources/core-external-data-workflow/-/issues/2 "EDS Preship test - fetch query does not respect wildcard syntax")
|
|
|
- Corrected Airflow [Xcom summary](https://urldefense.proofpoint.com/v2/url?u=https-3A__community.opengroup.org_osdu_platform_data-2Dflow_ingestion_external-2Ddata-2Dsources_core-2Dexternal-2Ddata-2Dworkflow\_-2D_issues_7&d=DwMFAg&c=eIGjsITfXP_y-DLLX0uEHXJvU8nOHrUK8IrwNKOtkVU&r=xyT-FeJSWBkH8qkgDyqzDmlFQPgSEWMh95lIMNoshfd14TcRm-PyeYRL64uc41GW&m=KvoovV3EbgucLHzgeCsGkR-0DkpYfDtyYqSLoXcqJw9_R7N1URARutOp7ecB31UZ&s=s_NGtT1cUISSbui_vSvYbjCZtyE43_j61oA-MKLqX7g&e=) from Ingest task
|
|
|
|
|
|
#### GCZ (Geospatial Consumption Zone)
|
|
|
### GCZ (Geospatial Consumption Zone)
|
|
|
|
|
|
* Transformer
|
|
|
* Fix `batchSize` config option not respected when below `1000`
|
... | ... | @@ -187,7 +187,7 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha |
|
|
- `Wellbore DDMS`
|
|
|
- API `POST /ddms/v3/records/delete` is deprecated, see [OpenAPI spec](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/blob/release/0.18/spec/generated/openapi.json). Consumers should use either the typed delete APIs from WDMS (e.g. `DELETE /ddms/v3/wells/{wellid}`) or the core storage service delete API.
|
|
|
|
|
|
#### GCZ (Geospatial Consumption Zone)
|
|
|
### GCZ (Geospatial Consumption Zone)
|
|
|
|
|
|
* Configuration file name change
|
|
|
* `application.yml` has been renamed to `application-local.yml`
|
... | ... | @@ -197,18 +197,14 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha |
|
|
|
|
|
<pre>
|
|
|
|
|
|
<span dir="">- </span>
|
|
|
<span dir="">- name: osdu:wks:master-data--Well:1.0.0 </span>\\ <span dir="">cacheName: osdu_wks_master-data--Well_1.0.0 </span>\\ <span dir="">chronExpr: 0 0 8 ?</span>
|
|
|
|
|
|
<span dir=""> name: osdu:wks:master-data--Well:1.0.0 </span>\
|
|
|
<span dir=""> cacheName: osdu_wks_master-data--Well_1.0.0 </span>\
|
|
|
<span dir=""> chronExpr: 0 0 8 ?</span>
|
|
|
|
|
|
</pre>\* The reason for this change is due to our new support of Persistence-Enabled Ignite Clusters, which strictly impose that cache names do not contain special characters such as \`:\` due to conflicts with file storage. Please note that taking the kind name and simply replacing all \`:\` characters with an underscore \`\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\_\` should work fine, but you are welcome to name your caches however you like, avoiding special characters.
|
|
|
</pre>\\\* The reason for this change is due to our new support of Persistence-Enabled Ignite Clusters, which strictly impose that cache names do not contain special characters such as \\\`:\\\` due to conflicts with file storage. Please note that taking the kind name and simply replacing all \\\`:\\\` characters with an underscore \\\`\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\_\\\` should work fine, but you are welcome to name your caches however you like, avoiding special characters.
|
|
|
* Additionally, you will need to configure `koop-config.json` to include the `cacheName` property or else the Provider will be unable to find the cache by `kind` entity alone.
|
|
|
|
|
|
## Known Issues/Gaps
|
|
|
|
|
|
#### GCZ (Geospatial Consumption Zone)
|
|
|
### GCZ (Geospatial Consumption Zone)
|
|
|
|
|
|
* WellLog support / Spatialization will only pull geometries from the `SpatialArea.Wgs84Coordinates` or `SpatialLocation.Wgs84Coordinates` properties from a record gathered via the Search API. By default, this is typically where Well records store their surface locations, and as such, Well Logs can only currently be displayed via the Surface Location of a Well, and **not** via the bottomhole or midpoint location.
|
|
|
|
... | ... | |