Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • I Ingestion DAGs
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Data Flow
  • Data IngestionData Ingestion
  • Ingestion DAGs
  • Issues
  • #81
Closed
Open
Issue created Jul 26, 2021 by Kamlesh Todai@todaiksDeveloper

While using manifest_ingestion (Osdu_ingest), the tags field for the Wellbore data is populated in the payload, it appears that the tags field is not getting ingested

The issue is that when the tags field for the Wellbore data is populated in payload while ingesting the wellbore data, it appears that the tags field is not getting ingested. There are no warnings or errors in the Airflow logs regarding this and the wellbore data is getting ingested, but the tags field is missing. Note: When tried to insert Wellbore data with tags field populated, using the storage API, it works fine. The details are attached in the word docs. tagsFieldIngestIssue.docx contains the payload used during ingestion and the queries done to check the tags field data. tagsFieldStorageSearch.docx contains the payload used while creating the wellbore record with tags field using the storage API The test was done on two platforms (AWS and GCP) The DAG/run details for the GCP { "workflowId": "ef82cba0-0e45-4df3-91bf-4df1553102d3", "runId": "22821aa9-82a2-4910-9e3f-d1e27addb49d", "startTimeStamp": 1627328994856, "endTimeStamp": 1627329575098, "status": "finished", "submittedBy": "kamlesh_todai@osdu-gcp.go3-nrg.projects.epam.com" }

The DAG/run details for the AWS runId: 57a9adc0-aabb-4bb9-8154-561b5c12412f

Have not tried on IBM and Azure to see whether the behavior is the same or different.

tagsFieldIngestIssue.docx

tagsFieldStorageSearch.docx

@ChrisZhang @ethiraj @debasisc @Wibben @Kateryna_Kurach @anujgupta @manishk

Edited Jul 26, 2021 by Kamlesh Todai
Assignee
Assign to
Time tracking