Using custom Destination

jitsucom / jitsu

Jitsu is an open-source Segment alternative. Fully-scriptable data ingestion engine for modern data teams. Set-up a real-time data pipeline in minutes, not days

https://jitsu.com

MIT License

4.11k stars 292 forks source link

Using custom Destination #713

Closed thanhlmm closed 2 years ago

thanhlmm commented 2 years ago

Problem

I want to use my own destination which is compatible with Airbyte, so I think it will be easy to add it to Jitsu

Solution

Make a function to add new Airbyte destination

vklimontovich commented 2 years ago

We support only Airbyte sources. For destinations, we use our own engine/specification.

What kind of destination you're looking to add? Maybe we have it already, or you can convert your code to our spec easily

thanhlmm commented 2 years ago

@vklimontovich do you have any doc to write destinations for Jitsu? I can't find it. I'm making a destination for Streamr Here is airbyte version: https://github.com/devmate-cloud/streamr-airbyte-connectors

vklimontovich commented 2 years ago

Hi @thanhlmm! We do have SDK for destinations: https://github.com/jitsucom/jitsu-sdk. However, it's in alpha, meaning:

API is not 100% fixed
It's not tested to work with events coming from "pull" sources

However, Mixpanel destination is already based on this SDK. If you're adventurous enough, we're happy to collaborate on Streamr destination ) Please, ping me on Jitsu Slack or email vladimir at jitsu dot com

thanhlmm commented 2 years ago

Great. I will ping you then