Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • R Register
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 5
    • Merge requests 5
  • 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
  • System
  • Register
  • Merge requests
  • !32

Fix datastore exception resolving (GONRG-921)

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Rustam Lotsmanenko (EPAM) requested to merge fix-datastore-exception-resolving into master Nov 03, 2020
  • Overview 0
  • Commits 11
  • Pipelines 8
  • Changes 4

Type of change

  • Bug Fix

Does this introduce a change in the core logic?

  • [NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Azure
  • GCP
  • IBM

Does this introduce a breaking change?

  • [NO]

What is the current behavior?

Response message comparison , doesn't look reasonable, messages can variate.

if (ex.getCode() == 10 && ex.getMessage().startsWith("too much contention"))

throw new AppException(409, "Conflict", "A DDMS already exists with the same id");

for example it can start with : "Aborted due to cross-transaction contention." while the code & reason of error the same.

What is the new/expected behavior?

Keep only response code comparison.

if (ex.getCode()== 10)

throw new AppException(409, "Conflict", "A DDMS already exists with the same id");

Details about error codes in doc : https://cloud.google.com/datastore/docs/concepts/errors#error_codes code 10 equal ABORTED code

Have you added/updated Unit Tests and Integration Tests?

  • [YES]

Any other useful information

depends on !31 (merged)

Edited Nov 11, 2020 by Rustam Lotsmanenko (EPAM)
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: fix-datastore-exception-resolving