jitsu
jitsu copied to clipboard
jitsucom
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
## Description Your github metrics etc. take almost 2 full minutes to show real data. (before that they all show zero's) ## Steps to reproduce Go to jitsu.com website ##...
### Problem For now we store user settings to local storage. localStorage is good for caching data, but never as a user settings storage. ### Solution Implement new api crud...
### Problem Currently patchTable checks difference between table schema in destination and table schema derived from data. But it ignores column type difference completely. So if column types differ we...
### Problem What problem this feature is going to solve. Why this problem is important Currently, we need to watch the Clickhouse tables with their columns on our end to...
### Summary We are going to implement Connector SDK as part of [Jitsu SDK](https://github.com/jitsucom/jitsu-sdk). The SDK should provide an easy way to develop jitsu connectors (aka sources) in TypeScript: *...
Problem of current design: * Events routing in Jitsu is hardcoded. * Also many components are hardwired. E.g. http handlers and destinations * Only 2 implementation of events queue supported:...
We need to officially support k8s: * Under k8 environement: Run airbyte source images as k8s pods instead of using DinD of DoD approaches * Add documentation with example of...
## The problem Destinations like BigQuery, Snowflake, Redshift in batch mode use GCS or S3 as an intermediately storage for batches. Instead of multiple inserts Jitsu uses `COPY` (or equivalent)...
## Environment - **Deploy method**: docker-compose.yml - **Jitsu version**: v1.40.2 - **OS**: ubuntu-s-1vcpu-1gb-sgp1-01 5.4.0-84-generic- - **Cloud Provider**: Digitalocean ## Description Destination and Source not display on configurator when using eventnative.yaml...
## Steps to reproduce Sync database source with more than one table. and events number in first table > airbyte batch size. ## Expected behavior All table cleared properly before...