Impulse Dev Manual
HomePricingContact Us
  • Understanding Impulse Sync
  • Understanding how Impulse diffs content
  • Understanding Job Scheduling
  • Motation
    • Content Motation
    • Definition Motation
    • Domain Motation
    • Folder Motation
    • Language Motation
    • Relationship Motation
    • Tag Motation
  • Connectors
    • Source Connector
    • Destination Connector
    • Go Code
    • IDs
    • ID Mapping
    • Testing Controller
      • Implementation
  • Motators Binary
    • Implementation
    • Go Code
  • Services
    • Connector Depot
    • Motator Binary Depot
    • Job Depot
    • Endpoint Depot
    • Sync Manager
    • Content Diffuser
    • Pickup Taxi
    • Dropoff Taxi
    • Pipeliner
    • Scheduler
    • Motator
    • Motator Service
  • Watchdog Process
    • Watchdog flow
  • Impulse License
  • Troubleshooting
    • Job Config
    • Transaction Audit Trail
  • gRPC
    • Protocol buffer compiler
  • Test Commands
  • Glossary
Powered by GitBook
On this page
  • Source Connector
  • Content ID
  • Version ID
  • Immutable ID
  • Content Diffuser
  • Content Hash
  • Version Hash
  • Local ID
  • Motation
  • Motation ID
  • Impulse ID
  • Destination Connector
  • Content ID
  • Field ID

Was this helpful?

  1. Connectors

IDs

PreviousGo CodeNextID Mapping

Last updated 2 years ago

Was this helpful?

Source Connector

Content ID

ID for a content that is unique and does not change when the content is updated.

Version ID

An ID that changes when the content updates. Or if the system does not create that type of ID, this should match the content id.

Immutable ID

Hash of a system id (inode, content id, etc.) and modification date for a content. It is an id that captures a point in time.

Content Diffuser

Content Hash

Equal to the

Version Hash

Equal to the .

Local ID

A hash of the endpoint ID + all version hashes.

Motation

Motation ID

The Motation ID is used for retrieving Motation objects from diesel.

Impulse ID

Impulse IDs are used for individual IDs in a Motation file. They are a segmented and hashed ID.

example:

9a0364b9e99bb480dd25e1f0284c8555.8af9d1b0bd2cf6b81743e2d9081d2901

The left of the . is a hash of the location of the id. Such as "Content" or "Relationship". There is an enum in the impulse-id go module which is a list of all possible locations.

The right of the . is a hash of the endpoint ID + the ID in the raw data from the system.

Destination Connector

Content ID

ID for a content that is unique and does not change when the content is updated.

Field ID

An ID for a field that is unique within the definition.

Motation ID for a Content Motation object matches from Content Diffuser. Motation Objects related to Content Motation will have the Local ID + Motation Object type.

Local ID
Local ID
Immutable ID