ilovesoup

3 ms·

1. 1.▲
   by ilovesoup 6y ago

   Well, its a lot easier to use TiFlash than replicating your OLTP data to a read-optimized database (whatever it is). 1. Add TiFlash nodes to your TiDB cluster (you might need to config some ports and ip address just like other databases and
2. 2.▲
   by ilovesoup 6y ago

   The reason for ClickHouse is simple: it's fast. And we need to have it function like a TiKV coprocessor which support filtering and aggregation mainly and ClickHouse is good at aggregation and filtering. Also it might take more time an
3. 3.▲
   by ilovesoup 6y ago

   I'm the product owner of TiFlash. Yes. We used ClickHouse as the compute engine for TiFlash. The project started as a modification of ClickHouse (more or less it still is). It was like "pushdown query to an actual OLAP database&qu
4. 4.▲
   by ilovesoup 7y ago

   (I'm a dev of TiDB so I might be biased.) Yes and no. The yes part is that TiDB still rely on TiSpark for large join query as well as bridging big-data world. TiDB itself cannot shuffle data like MPP database yet. On the other hand, T
5. 5.▲
   by ilovesoup 9y ago

   I'm the main dev of TiSpark. I totally agree. For now we allow trx only in TiDB. I believe one day those big-data stuff will be unified onto one platform. With a full-featured distributed db storage layer underneath, there might be ton