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-3.0.2rc269.tar.gz (18.1 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

car_connector_framework-3.0.2rc269-py3-none-any.whl (22.4 kB view details)

Uploaded Python 3

File details

Details for the file car-connector-framework-3.0.2rc269.tar.gz.

File metadata

File hashes

Hashes for car-connector-framework-3.0.2rc269.tar.gz
Algorithm Hash digest
SHA256 b60ff9b841cf2ae6a31a6f1435128ce51559bae7f8ce9f1cbaf365f4bcb28ae8
MD5 00c9240947a974586f8f1475793dc523
BLAKE2b-256 8401167c3b7aa3f9ea8a0f0fc27b2084a8f053d2e301d2a9abe5ea360f566f92

See more details on using hashes here.

File details

Details for the file car_connector_framework-3.0.2rc269-py3-none-any.whl.

File metadata

File hashes

Hashes for car_connector_framework-3.0.2rc269-py3-none-any.whl
Algorithm Hash digest
SHA256 a2dafbd9c2e81a0b9dbc6a8961cee1fa49ff8d5664dc4fd5cfff81483ff8e2d4
MD5 bba16238fbd17e0953d01a5fd7e460e0
BLAKE2b-256 441226b10477241aaa0fc21175a4601f864cfe3de96a4484c643114ddf07da1a

See more details on using hashes here.

Supported by

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