EDS M25 Release Notes and Test Summary
EDS M25 Patches Releases
Click link to know the fixes:
- Patches: 0.28.0 & 0.28.1 -> 0.28.2
- Patches: 0.28.2 -> 0.28.3
- Patches: 0.28.3 -> 0.28.4
- Patches: 0.28.4 -> 0.28.5
- Patches: 0.28.5 -> 0.28.6
EDS M25.1 Patches Releases
Environment Variable Changes
| Patches Release | Environment Variable Required |
|---|---|
| 0.28.0, 0.28.1, 0.28.2 |
|
| 0.28.3, 0.28.4 |
|
| 0.28.5 and onwards |
|
EDS M25 Known Issues
- (EDS) EDS: Add release versions in Airflow Logs, Activity Template (#147) · Issue
- (EDS Ingest - Activity template logging) EDS Activity template enhancement for Osdu_ingest_by_reference and validation error (#144) · Issues
- (EDS Ingest) Check RefreshToken Authentication - auto-refresh token for refresh token (#145) · Issues
- (EDS Ingest) Azure M25: EDS Ingestion Failure: Exception thrown while validating for ExternalReferenceValueMapping (#752)
- (EDS Ingest) M25 EDS - Mapped Master data - Complex Mapping (#165) · Issue
- (EDS Ingest) M25 EDS - Multiple conditions in ParentMatchingRuleSets for same kind ignored (#166) · Issue
- (EDS Email Notification) Scalable Email Notification Authentication (#136) · Issue
- (EDS Naturalization) EDS Naturalization: Error message hardening during re-naturalization of same record (#156) · Issue
- (EDS Naturalization) Airflow run died unexpectedly before EDS Naturalization (#751) · Issue
- (Dataset Service) Dataset Service - Documentation Status Code Update (#125)
- (Workflow Service) ADR: Workflow Versioning and Update Workflow API (#136) · Issues
- (OS Core Common) Enhance Info Endpoints to Display Feature Flag Status (#86) · Issues
- (Airflow) ADR: Airflow dependency isolation and KubernetesPodOperators (#55) · Issue
M25 Release - Functionality/Testing Scope
The table below is the new functionality or bugs for M25 (excluding the basic functionality). The basic functionality can be found in the first discussion excel below.
| Feature/Issue Name | Testing Check List | Overview | To Check | Documentation Link | Recording Link | Action Item | |
|---|---|---|---|---|---|---|---|
| 1 | Unable to trigger the EDS ingest from Airflow UI |
[Airflow UI] Able to trigger DAGs from Airflow UI |
Testing Artifact:https://community.opengroup.org/-/project/407/uploads/b8384598dc92141c9734817e460f4b10/EDS-PreShip-Test-Session1.docx |
EDS Community meeting: |
|||
| 2 |
|
User is having hard time to understand the xcom summary |
[Airflow UI] From Airflow UI, check the xom summary |
Testing Artifact:https://community.opengroup.org/-/project/407/uploads/b8384598dc92141c9734817e460f4b10/EDS-PreShip-Test-Session1.docx |
EDS Community meeting: |
||
| 3 |
eds_naturalization DAG doesn't use correct schema authority (#141) |
|
On a multiple schema authority instance, we want to honor the trusted schema authority by using the env variable from Airflow |
[Airflow UI] [EDS Ingest] [EDS Naturalization] Airflow variable contains schema authority and able to run EDS Ingest and EDS naturalization |
|||
| 4 |
ADR: EDS Ingest - Push Functionality using Workflow API (#74) · |
User can manually Trigger via Workflow API |
[EDS Ingest] Able to trigger workflow API with custom filter |
EDS Configuration Guide - OSDU EDS Documentation Testing Artifact:https://community.opengroup.org/-/project/407/uploads/b8384598dc92141c9734817e460f4b10/EDS-PreShip-Test-Session1.docx |
EDS Community meeting: |
||
| 5 |
Secret Service V2 adoption - EDS fetch and Ingest (#64) · Issues · |
|
User's OSDU instance might be running on Secret Service V1/V2 |
[EDS Ingest] EDS able to run on Secret Service V1 and V2 instance |
Testing Artifact:https://community.opengroup.org/-/project/407/uploads/b8384598dc92141c9734817e460f4b10/EDS-PreShip-Test-Session1.docx |
EDS Community meeting: |
|
| 6 |
|
In the CSDJ record, the |
[EDS Ingest] After EDS ingest process is completed, check on the
|
Testing Artifact:https://community.opengroup.org/-/project/407/uploads/b8384598dc92141c9734817e460f4b10/EDS-PreShip-Test-Session1.docx |
EDS Community meeting: |
||
| 7 |
|
During an ingestion, the |
[EDS Ingest] After EDS ingest process is completed, check on the
|
Testing Artifact:https://community.opengroup.org/-/project/407/uploads/b8384598dc92141c9734817e460f4b10/EDS-PreShip-Test-Session1.docx |
EDS Community meeting: |
||
| 8 |
Id replacement “osdu:” to “osdu:osdu:”. Needs investigation and fix. (#126) · Issues · |
|
Before M24, the query should (kind:id). After M24 onwards, the query will be (partition:kind:id) |
[EDS Ingest] In CSDJ, |
Testing Artifact:https://community.opengroup.org/-/project/407/uploads/b8384598dc92141c9734817e460f4b10/EDS-PreShip-Test-Session1.docx |
EDS Community meeting: |
|
| 9 | Katalyst would like to pass a signed url so that Naturalization could download the file from the signed url and upload to dataset service |
[EDS Naturalization] Pass in the signed url under the |
|||||
| 10 |
Modify naturalization Dag file to improve time complexity (#111) · Issues · |
|
Perform optimization on the naturalization DAG file for optimization |
[EDS Naturalization] Able to run Naturalization |
N/A | ||
| 11 |
|
Incremental updates on email notification and without redundancy |
[EDS Ingest] [EDS Scheduler] Able to received email notification without redundant jobs updates |
||||
| 12 |
|
User would like to ingest reference data into the OSDU system |
[EDS Ingest] Able to ingest reference data via manifest ingestion and manifest by reference |
Todo Secondary testing for manifest by ref | |||
| 13 |
Enhancement in Complex Parent data mapping functionality (#134) · |
User would like to perform various kinds of complex parent data mapping (ie. name alias matching and geoTypeId name matching |
[EDS Ingest] Able to run complex parent data mapping logic |
||||
| 14 |
Enhance Reference Data Mapping as per XOM suggestion[Techdebt] (#68) |
|
User would like to have refer to a reference data from a data provider within an CSRE or reference data from the OSDU system |
[EDS Ingest] Able to map the reference data based on the configuration of choosing data providers' or OSDU system |
|||
| 15 |
RequestBodyTooLarge exception in EDS ingest for large payload. (#125) · Issues |
In Azure Preship, EDS Ingest payload isn't calculated properly that leads to incorrect redirection of ingestion strategy |
[EDS Ingest] EDS is able to choose the correct ingestion strategy based on the records size that needs to be ingested |
||||
| 16 |
Store manifest_by_reference Run Details in Activity template (#115) · |
|
User is able to search for |
[EDS Ingest] The content of the records and XCOM are consistent |
|||
| 17 |
ADR: EDS Triggering & Monitoring Custom Post Processing API (#120) |
|
User is able to trigger and/or monitor a custom post processing API based on their configuration that should follow EDS implementation requirements |
[EDS Ingest] [EDS Naturalization] In post-ingest or post-naturalization, the EDS is able to trigger and/or monitor a custom post processing API |
Testing Artifact: https://community.opengroup.org/-/project/407/uploads/b8384598dc92141c9734817e460f4b10/EDS-PreShip-Test-Session1.docx |
EDS Community meeting: |
|
| 18 |
EDS DMS
EDS Naturalization
|
In compliancy with CI environment, EDS DMS and EDS Naturalization should be able to run on CI |
[EDS Naturalization] EDS DMS is able to retrieve an external file from provider using Dataset service EDS Naturalization is able to download and upload the external file to the operator OSDU instance |