Sergey Burykin

### Problem At the moment Jitsu has two servers with JSON-based APIs: - Configurator - Server Both of them have manual API documentation which are not always in sync with...

### Problem At present Jitsu creates string columns with `TEXT` or `character varying(65535)` SQL type even if they are used in the primary key constraint. Downside: data type `text` requires...

### Problem At present Jitsu writes data from sources into destinations (data warehouses) without any SQL typecasts. Sometimes it leads to SQL types errors. We should improve it by adding...

### Problem When Jitsu does full re-sync in sources synchronization, it truncates the destination table before writing data. Since the source's discovered catalog might be changed between syncs and destination...

### Problem At present Jitsu adds `${source_id}_` prefix to the destination tables on source synchronization. We should give users more control and make this field configurable on UI. ### Solution...

### Problem BQ does not support [data mutation](https://cloud.google.com/blog/products/data-analytics/dml-without-limits-now-in-bigquery) in a reliable and fast fashion. That creates certain problems when BQ is used as a destination for pull sources: * **Native...

# Problem At the moment, we have following issues with [Retroactive User Recognition](https://jitsu.com/docs/other-features/retroactive-user-recognition) * BigQuery — retroactive user recognition not implemented at all * RedShift, Snowflake — updates works through...

### Problem Jitsu writes error logs without a stack trace. It means that you can find a problem by error log message, but it can be inconvenient in the case...

### Problem On every incoming event, Jitsu writes JSON payload to the separate in-memory queue in (`server/users/service.go func Event()`). It can lead to increased RAM consumption. It is possible to...

### Problem At present Jitsu doesn't measure performance, but it is nice to have feature: know about what time does an event need to be written into DWH. ### Solution...