e63d371e10
* timeplus destination connector to push data to Timeplus via REST API/SDK
* 0.2.0, support nullable columns, add more test data
boolean and pokemon
* mark the apikey as secret
* us.timeplus.cloud as sample URL
* removed the unnecessary pass
* rewrite the logic of when to delete/create stream
* format code, following the PEP-8
* add write integration test
* replacing AirbyteLogger() with logging.getLogger('airbyte')
* add logs to destination.py, refine integration test
* add docs/integrations/destinations/timeplus.md
* add icon.svg
* set to 0.4.0 version
* upgrade timeplus sdk from 1.1.1 to 1.2.1
* add metadata file
* fix docker version
---------
Co-authored-by: marcosmarxm <marcosmarxm@gmail.com>
Co-authored-by: Marcos Marx <marcosmarxm@users.noreply.github.com>
1.3 KiB
1.3 KiB
Timeplus
This page guides you through the process of setting up the Timeplus destination connector.
Features
| Feature | Supported?(Yes/No) | Notes |
|---|---|---|
| Overwrite | Yes | |
| Incremental - Append Sync | Yes |
Output Schema
Each stream will be output into its own stream in Timeplus, with corresponding schema/columns.
Getting Started (Airbyte Cloud)
Coming soon...
Getting Started (Airbyte Open-Source)
You can follow the Quickstart with Timeplus Ingestion API to createa a workspace and API key.
Setup the Timeplus Destination in Airbyte
You should now have all the requirements needed to configure Timeplus as a destination in the UI. You'll need the following information to configure the Timeplus destination:
- Endpoint example https://us.timeplus.cloud/randomId123
- API key
Compatibility
Changelog
| Version | Date | Pull Request | Subject |
|---|---|---|---|
| 0.1.0 | 2023-06-14 | 21226 | Destination Timeplus |