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
    • 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
  • #77
Closed
Open
Issue created Jul 14, 2021 by kenneth liew@kennethliewDeveloper

[R3-M8]Issue with “frame of reference” handling (Unit of Measure) by Manifest-based Ingestion [GONRG-3041]

The case is related to the unit conversation with the environment R3-M5 (Katalyst private AWS setup).

Related to “master-data—SeismicAcquisitionSurvey” entity.

Test case-1 : I verified that Normalizer (Indexer) does perform auto-conversion as expected when we persist using storage service.

Test case-2 : However, it does not perform auto-conversion when we persist data using manifest-based ingestion.

My test case uses length values in "feet" and I do see converted values (meter) from Search Service query in the first test case.

I also noticed that the “meta”’s details are missing on that record by using the “Storage Get” method after inserting the record by manifest ingestion.

I have attached some examples related to this issue. Please focus on the blue highlight at the "ManifesIngestionMethod.docx" document.

FYI @debasisc

ManifestIngestionMethod.docx StorageMethod.docx

Edited Oct 02, 2021 by Debasis Chatterjee
Assignee
Assign to
Time tracking