@@ -13,21 +14,21 @@ OSDU R3 Milestone 6 is released on Jul 2, 2021. For detailed services that are i
...
@@ -13,21 +14,21 @@ OSDU R3 Milestone 6 is released on Jul 2, 2021. For detailed services that are i
*`WITSML Ingestion` now available on `GCP`
*`WITSML Ingestion` now available on `GCP`
*`Entitlement V2` Updated [Entitlement service](https://community.opengroup.org/osdu/platform/security-and-compliance) is now available on `AWS``Azure`
*`Entitlement V2` Updated [Entitlement service](https://community.opengroup.org/osdu/platform/security-and-compliance) is now available on `AWS``Azure`
## Bug Fixes
## Bug Fixes
*`Search` Aggregations on Text fields using Search is Allowed.
*`Search` Aggregations on Text fields using Search is Allowed.[More details](https://community.opengroup.org/osdu/platform/system/search-service/-/issues/37).
*`Search` Record Count (```total_cout```) clipping at 10K in Ealstic 7.x issue is fixed.
*`Search` Record Count (`total_cout`) clipping at 10K in Ealstic 7.x issue is fixed.[More details](https://community.opengroup.org/osdu/platform/system/search-service/-/issues/29).
*`Ingestion` Special Characters are handles in Energistics Parser.
*`Ingestion` Special Characters are handles in Energistics Parser.[More details](https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics-osdu-integration/-/issues/30).
*`Ingestion` WITSML parser error caused by missing symbol at the end of reference Ids resolved.
*`Ingestion` WITSML parser error caused by missing symbol at the end of reference Ids resolved.[More details](https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics-osdu-integration/-/issues/29).
*`Ingestion` Made Energistics parser produces output comliance with R3 Schemas.
*`Ingestion` Made Energistics parser produces output compliance with R3 Schemas. [More details](https://community.opengroup.org/osdu/platform/data-flow/ingestion/energistics-osdu-integration/-/issues/28).
## Breaking Changes
## Breaking Changes
* None
* None
## Known Issues
## Known Issues
-`New Policy Service` is an experimental feature, meant to be deployed in a dedicated test partition for evaluation and community feedback. It is not recommended to be enabled in production environments as any potential impact to other services is yet to be fully assessed
-`Admin UI` Authentication issue may be experienced on environments configured with updated Entitlements version 2 (EV2) when performing login/logout. `AWS``Azure`
*`New Policy Service` is an experimental feature, meant to be deployed in a dedicated test partition for evaluation and community feedback. It is not recommended to be enabled in production environments as any potential impact to other services is yet to be fully assessed
-`Entitlement V2` Call for adding a user fails if the email id had a subdomain name which is same as data partition id. [Issue in Gitlab](https://community.opengroup.org/osdu/platform/security-and-compliance/entitlements/-/issues/72) is under investigation.
*`Admin UI` Authentication issue may be experienced on environments configured with updated Entitlements version 2 (EV2) when performing login/logout. `AWS``Azure`
-`Re-indexing`: Re-indexing is not part of most of the normal workflows that the user would be executing. However, during testing when re-indexing API was used to re-index the data, a potential issue was found which needs to be investigated and clarified, as to why the reloading of data was required after calling the re-index API to re-index the data. [Issue in Gitlab](https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/26)
*`Entitlement V2` Call for adding a user fails if the email id had a subdomain name which is same as data partition id. [Issue in Gitlab](https://community.opengroup.org/osdu/platform/security-and-compliance/entitlements/-/issues/72) is under investigation.
*`Re-indexing`: Re-indexing is not part of most of the normal workflows that the user would be executing. However, during testing when re-indexing API was used to re-index the data, a potential issue was found which needs to be investigated and clarified, as to why the reloading of data was required after calling the re-index API to re-index the data. [Issue in Gitlab](https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/26)
