tang8330

For now, we're super focused on databases as sources. We really want to do this well before we move on to other data sources such as APIs.

Thank you!!

Definitely. Do you expect the resulting data to also be in binary / bytes format in your DWH? I ask because there's a workaround by setting `binary.handling.mode` to a STRING type [1]. Trans…

That's fascinating! Thanks for providing more color, support for geometric shapes coming! https://github.com/artie-labs/transfer/issues/155 …

Eventual consistency FTW!

Main value props are low latency OLTP data in your DWH and lower DWH ingestion costs.

Great question! Say this happened: * CREATE TABLE user_test (id int primary key, name text); * INSERT INTO user_test (id, name) VALUES (1, 'foo'); * UPDATE user_test set id = 2 where id = 1;…

For us, what we are striving to do differently is: 1/ DFS vs BFS. We are planning on rolling out connectors slowly vs. building tens / hundreds / thousands of connectors to try to attra…

> Hey, brief feedback, but "5,000,000,000+" rows processed might be a red flag for some. Many individual customers might do this per day, so to say that's all the company has done so…

Not at the moment, but no reason(s) why we shouldn't. Debezium already supports this [1] and it'd be a minor refactor on our end to support. If that's something you'd want, LMK! [1…

Hey HN, We're thrilled to release our public version of Artie Transfer! Artie Transfer leverages change data capture (CDC) in order to provide the sub-minute latency between transactional DBs and…