@@ -30,45 +30,37 @@ include the following fragments - see more details in [Migration Guides](https:/
* Seismic acquisition/pre-stack related reference value types, [details](https://community.opengroup.org/osdu/data/data-definitions/-/blob/v0.13.0/ReferenceValues/ChangeLogs/M10/README.md#new-seismic-reference-data)
* New reference value type for geo-reference image `GeoReferencedImageType`, `TechnicalAssurance`
* Storage API query optimization for `Azure` - [Refer to Issue 106](https://community.opengroup.org/osdu/platform/system/storage/-/issues/106).
*`Data Ingestion`
*`Airflow` 2 is now supported by all CSPs. The detailed versions from CSPs are:
* Airflow 2.1.2 is now available for `Azure`.
* Airflow 2.2.3 is now available for `AWS`.
* Airflow 2.1.4 is now available for `GCP`.
* Airflow 2.1.1 is now available for `IBM`.
* Airflow 2.1.2 is now available for `Azure`
* Airflow 2.2.3 is now available for `AWS`
* Airflow 2.1.4 is now available for `GCP`
* Airflow 2.1.1 is now available for `IBM`
*`Manifest ingestion` is supported by all CSPs.
*`frame of reference conversion` for `AWS` is yet to be validated
*`Manifest ingestion` is supported by all CSPs
*No new features added for R3M10
*`CSV ingestion` is supported by `Azure`, `GCP`, `IBM`
*CSV ingestion on AWS is planned to be supported in M11
*No new features added for R3M10
*`WITSML ingestion`
*`Trajectory` component validated for `Azure`, `GCP`.
*`Welllog` component validated for `GCP`.
*`Well/Wellbore information` component validated for `Azure`, `GCP`, `IBM`.
*`WITSML ingestion` is supported by all CSPs
* No new features added for R3M10
*`DDMS`
*`Wellbore DDMS`
* Added `TechnicalAssuranceID` support in `AbstractCommonResources`.
* Performance improvement in large loading jobs.
* Refactoring WDMS to handle large number of curves in an efficient manner. [Refer to issue](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/issues/35"Handle large number of curves").
*`Wellbore DDMS` is supported by all CSPs
* Added `TechnicalAssuranceID` support in `AbstractCommonResources`
* Performance improvement in large loading jobs
* Refactoring WDMS to handle large number of curves in an efficient manner. Refer to [issue](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/issues/35"Handle large number of curves")
* Added limit to 500 columns maximum per chunk when sending data
* Memory leak with data chunking is partially fixed. Find the issue [here](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/issues/26"memory leak with data chunking").
* Available on `AWS`, `Azure`, `GCP`, `IBM`.
* Memory leak with data chunking is partially fixed. Refer to [issue](https://community.opengroup.org/osdu/platform/domain-data-mgmt-services/wellbore/wellbore-domain-services/-/issues/26"memory leak with data chunking")
*`Seismic DDMS`
* OpenVDS workflow – a hook to catalog information has been provided. Refer [here](https://community.opengroup.org/osdu/platform/data-flow/ingestion/segy-to-vds-conversion/-/issues/5"Provide hook to Catalog information (ex: SeismicTraceData work-product component)") for detailed notes.
*`segY-oZGY` for `Azure`, `GCP`, `IBM` validated.
*`segY-oVDS` is yet to be validated.
*`Seismic DDMS` is supported by `Azure`, `GCP`, `IBM`
* OpenVDS workflow – a hook to catalog information has been provided. Refer [here](https://community.opengroup.org/osdu/platform/data-flow/ingestion/segy-to-vds-conversion/-/issues/5"Provide hook to Catalog information (ex: SeismicTraceData work-product component)") for detailed notes
*`Well Delivery DDMS`
* Well Delivery is released with official Data Definition.
*`Admin UI`
* Available for `GCP`.
*`Well Delivery DDMS` is supported by `GCP`, `IBM`
* Well Delivery is released with official Data Definition
## Bug Fixes
...
...
@@ -93,13 +85,21 @@ include the following fragments - see more details in [Migration Guides](https:/
* Log Recognition API returns `404 Family Not Found` error instead of `400 Bad Request` in case the requested Family is not recognized.
## Known Issues/Gaps
* _There is a known gap in validation due to shortage of time and resources_
*`Core Services`
* Storage API query optimization for `Azure` - [Refer to Issue 106](https://community.opengroup.org/osdu/platform/system/storage/-/issues/106).
*`Manifest Ingestion`
*`frame of reference conversion` for `AWS` is not working due to [issue 246](https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/246).
*`WITSML Ingestion`
* Reference data search limit in ingestion core lib for `AWS`, `Azure`, `IBM`. Refer to [issue](https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/245)
* Reference data search limit in ingestion core lib. Refer to [issue]
*`Trajectory` component validated for `Azure`, `GCP`.
*`Welllog` component validated for `GCP`.
*`Well/Wellbore information` component validated for `Azure`, `GCP`, `IBM`.(https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/245)
*`CSV Ingestion`
* CSV ingestion on `AWS` is planned to be supported in M11.
*`Seismic DDMS`
* Support on `AWS` is yet to be validated.
*`segY-oZGY` pending validation on `AWS`
*`segY-oVDS` pending validation on all CSPs
*`Well Delivery DDMS`
* Support on `AWS` is not available due to [issue 237](https://community.opengroup.org/osdu/platform/pre-shipping/-/issues/237).
