synsqlbythesea

4 ms·

1.
by synsqlbythesea 3mo ago
Hi Islambaraka. Thank you for your question. You have hit on an important design choice. SynSQL relies on a strict fan out across all partitions. - Wide tables: As you can see on the multi_omic live demo, queries include the hash key. And
2.
Show HN: SQL service for tables with billions of rows or up to 1M columns
4 points by synsqlbythesea 3mo ago|3 comments
3.
by synsqlbythesea 9mo ago
That’s a fair question! A concrete case where this comes up is multi-omics research. A single study routinely combines ~20k gene expression values, 100k–1M SNPs, thousands of proteins and metabolites, plus clinical metadata — all per patien
4.
by synsqlbythesea 9mo ago
Thanks — both are great systems. ClickHouse and Scuba are extremely good at what they’re designed for: fast OLAP over relatively narrow schemas (dozens to hundreds of columns) with heavy aggregation. The issue I kept running into was extrem
5.
by synsqlbythesea 9mo ago
From what I understand, Exasol is a very fast analytical database for traditional data warehouses. My engine doesn't replace a data warehouse; it solves a type of table that data warehouses simply can't handle: tables with hundred
6.
by synsqlbythesea 9mo ago
In a few words: table data is stored on hundreds of MariaDB servers. Each table is user designed hash key columns(1->32) to manage automatic partitioning. Wide tables are split in chunks. 1 chunk = the hash key + columns = one MariaDB s
7.
Ask HN: Distributed SQL engine for ultra-wide tables
23 points by synsqlbythesea 9mo ago|20 comments