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.2rc280.tar.gz (18.2 kB view details)

Uploaded Source

Built Distribution

File details

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

File metadata

File hashes

Hashes for car-connector-framework-3.0.2rc280.tar.gz
Algorithm Hash digest
SHA256 c11378876e29e716a875f1611c65de51c72242d6c893831984730bd2fc8502b6
MD5 d5c35a9dc80cf2a80c1bdb12922288a7
BLAKE2b-256 330a21aeec14256c126dd3023584329d2226e86827637dc50e09783ea269d350

See more details on using hashes here.

Provenance

File details

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

File metadata

File hashes

Hashes for car_connector_framework-3.0.2rc280-py3-none-any.whl
Algorithm Hash digest
SHA256 ff84e358350ea5129912cf0054f373152910eb579ba90f05eb9080b95a84d20d
MD5 4e5c6a64d771f01306c189f7db720185
BLAKE2b-256 d84afefe1c1dd79c9253aa5fed6e1c7553029403a1d2a244adf91c7d0ec994df

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