Vladimir Klimontovich

After authdash server refactoring endpoint changed it's format to: ``` [ .... { "id": "google_analytics", "type": "GOOGLE", "secrets": { "clientId": "•••••••••••••", "clientSecret": "•••••••••••••" }, } .... ``` The biggest change...

The whole user recognition flow relies on the fact that we could pull user by anonymous_id relatively quickly. Besides redis following storages will work: - `S3`. Unlike regular file system,...

The easiest way to implement that is to make a [destination plugin](https://jitsu.com/docs/extending/destination-plugins) that sends data to Elastic via [REST API](https://www.elastic.co/guide/en/elasticsearch/reference/current/rest-apis.html). Unfortunately, we don't have a capacity to develop this plugin...

Hi @gervarela ! It makes sense. Just to clarify the use-case, the pipleline you're talking about will look like: Tracker (JSON) → EventNative → Kafka? EventNative will send JSON to...

Note on json paths: syntax should be `a.b.c` or `/a/b/c`. If the latter, `a` should be equivalent to `/a`

@azhard4int we'll take a look. Probably that's something we can release mid-October. However, I don't think `session` is a good description of this feature. Usually, sessions are a sequence of...

Hi @azhard4int! Not this month :( Maybe in December. Maybe it would make sense to implement that on your frontend? I believe this package will do the job: https://github.com/jasonzissman/TimeMe.js/ You...

Let also add custom transformations of Airbyte source config before sending it to server. CC @jfk9w

It's a good candidate for implementing with new [Jitsu SDK](https://github.com/jitsucom/jitsu-sdk)

@absorbb let's keep this open anyway. The best solution would be stop flattening at any node that has an explicit typing (it could be `JSON`, `TEXT` or any other type