Skip to main content

CAR service connector framework

Project description

Car Connector Framework

Develop a connector

Use connectors/reference_connector from cp4s-car-connectors project as an example of how this framework is to be used.

A CAR connector project will need to extend the framework classes: BaseFullImport, BaseIncrementalImport, BaseApp, BaseAssetServer and BaseDataHandler, and implement abstract methods of those classes.

Things to note:

  • All communications with CAR digestion microservice are managed by the framework. Connector code normally does not need to access CAR digestion microservice directly

  • The framework is trying to make some intelligent choice for whether to run full vs incremental import. Normally, for performance reasons we would always prefer to run incremental import if one is possible. Some examples of when it is not possible are:

    • The model states for generating delta are not available
    • The model on the CAR side is empty
    • The previous incremental import session failed and a new incremental import session can potentially create a gap in the model data
  • Because of the above the the connector code should properly use (throw/raise) one of three following exceptions when detecting failures:

    • RecoverableFailure is to be used when the failure cannot potentially create a data gap and we can attempt an incremental import session when running next time. One example of a recoverable failure is a connectivity problem.
    • UnrecoverableFailure is to be used when the failure can potentially create a data gap and we must run full import session to recover.
    • DatasourceFailure is to be used when there is datasource API issues.

RecoverableFailure and UnrecoverableFailure are mostly handled in the framework. DatasourceFailure is to be used in the connector code with a corresponding error code. Example: return ErrorCode.TRANSMISSION_AUTH_CREDENTIALS.value. If none of the Failure classes is used, the framework will raise a GENERAL_APPLICATION_FAILURE (Unknown error) and print the error stack.

For more information use guides

Test deploy

https://github.com/IBM/cp4s-car-connectors/blob/develop/deployment/README.md

Publish

Use the guide from PUBLISH.md

Project details


Release history Release notifications | RSS feed

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

car-connector-framework-4.0.0rc51.tar.gz (18.1 kB view details)

Uploaded Source

Built Distribution

File details

Details for the file car-connector-framework-4.0.0rc51.tar.gz.

File metadata

File hashes

Hashes for car-connector-framework-4.0.0rc51.tar.gz
Algorithm Hash digest
SHA256 b355be781570741c95fb8f959f70f405afe7f906b662f34e4eab5338d9c07800
MD5 deb8afc21361742e29624c1a9cafbb63
BLAKE2b-256 faf69aa008e5b8e83ebaf7d696c4db45970392bc9fd2e0804c3ff08e48cfcff6

See more details on using hashes here.

Provenance

File details

Details for the file car_connector_framework-4.0.0rc51-py3-none-any.whl.

File metadata

File hashes

Hashes for car_connector_framework-4.0.0rc51-py3-none-any.whl
Algorithm Hash digest
SHA256 83a55a291b1087ba3ca62e20a4473d459d06f22d543f619214223dcb835f9813
MD5 32eb52a681b19d816bb7d552e37f358e
BLAKE2b-256 1c5a8401eda4269b6d489309440a4f5803ef580d88bd29bc2c24a3bbe65e4d6b

See more details on using hashes here.

Provenance

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page