Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
P
platform
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 157
    • Issues 157
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • simantics
  • platform
  • Issues
  • #643

Closed
Open
Opened Nov 20, 2020 by Marko Luukkainen@luukkainenOwner

Configure TG import failOnMissingEntities on code level.

At the moment fail on missing entities can be configured only with "failOnMissingEntities" system property. This approach has following limits:

  • You cannot have different behaviour on different TG-based imports.
  • If data processing expects fail on missing, and launch configuration does not include system property, the result of a import is potential DB semantic corruption that the software cannot handle, leading to data loss. (Or customers sending their databases to us for debugging)
Assignee
Assign to
1.43.1
Milestone
1.43.1
Assign milestone
Time tracking
None
Due date
None
Reference: simantics/platform#643