Update M15 Release Notes authored by Laurent Deny's avatar Laurent Deny
...@@ -53,6 +53,10 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha ...@@ -53,6 +53,10 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha
- `Wellbore DDMS` - `Wellbore DDMS`
- Support of Well 1.2.0 and [Wellbore 1.2.0](https://community.opengroup.org/osdu/data/data-definitions/-/blob/v0.18.1/E-R/master-data/Wellbore.1.2.0.md), see [!#656](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/merge_requests/656) - Support of Well 1.2.0 and [Wellbore 1.2.0](https://community.opengroup.org/osdu/data/data-definitions/-/blob/v0.18.1/E-R/master-data/Wellbore.1.2.0.md), see [!#656](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/merge_requests/656)
- `Reservoir DMS`
- REST API capability to create manifest information from RDMS content at the end of collaboration workflow, allows to provide outside information such as ACL, legal tags and existing dataset reference
- Server capability to clone dataspace
### External Data Services (EDS) ### External Data Services (EDS)
- Enable the end-user to configure [schema authority variable](Enable the end-user to configure schema authority variable at the Data Operator side) at the Operator end - Enable the end-user to configure [schema authority variable](Enable the end-user to configure schema authority variable at the Data Operator side) at the Operator end
- Handle EDS [incremental fetch](https://community.opengroup.org/osdu/platform/data-flow/ingestion/external-data-sources/external-data-framework/-/issues/252) scenario - Handle EDS [incremental fetch](https://community.opengroup.org/osdu/platform/data-flow/ingestion/external-data-sources/external-data-framework/-/issues/252) scenario
...@@ -77,6 +81,9 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha ...@@ -77,6 +81,9 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha
- lib updates: [fastAPI 0.70](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/merge_requests/659), [Dask 2022.10.2](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/merge_requests/612), [ffspec and implementations (adfs, s3fs, gcfs ...)](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/merge_requests/612), [PyArrow 9.0.0](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/merge_requests/649). - lib updates: [fastAPI 0.70](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/merge_requests/659), [Dask 2022.10.2](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/merge_requests/612), [ffspec and implementations (adfs, s3fs, gcfs ...)](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/merge_requests/612), [PyArrow 9.0.0](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/merge_requests/649).
- Azure lib: retry mechanism to work around ClientAuthentication issues to blob storage (see [changes](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/lib/wellbore-cloud/wellbore-azure-lib/-/merge_requests/36), imported by [!659](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/merge_requests/626)). - Azure lib: retry mechanism to work around ClientAuthentication issues to blob storage (see [changes](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/lib/wellbore-cloud/wellbore-azure-lib/-/merge_requests/36), imported by [!659](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/merge_requests/626)).
- `Reservoir DMS`
- Fixes around entitlement and group management
### External Data Services (EDS) ### External Data Services (EDS)
- [EDS-Ingest](https://community.opengroup.org/osdu/platform/data-flow/ingestion/external-data-sources/core-external-data-workflow/-/issues/3) - show in the Airflow log the exact body of the query being executed to bring data from the source - [EDS-Ingest](https://community.opengroup.org/osdu/platform/data-flow/ingestion/external-data-sources/core-external-data-workflow/-/issues/3) - show in the Airflow log the exact body of the query being executed to bring data from the source
- 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) - 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)
...@@ -90,11 +97,6 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha ...@@ -90,11 +97,6 @@ No in-place schema changes are required in M15 (no M14 schema resources were cha
- `Wellbore DDMS` - `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. - 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.
- `Reservoir DMS`
- REST API capability to create manifest information from RDMS content at the end of collaboration workflow, allows to provide outside information such as ACL, legal tags and existing dataset reference
- Server capability to clone dataspace
- Fixes around entitlement
### Known Issues/Gaps ### Known Issues/Gaps
## Supporting Information ## Supporting Information
... ...
......