This is a really good question. My snarky answer is "the way we ingest JSON doesn't require 50 pages and n configuration settings to explain."
Here's a more factual one:
- We don't use tuples for nested JSON. We just use underscores to show parent_child relationships in keys.
- We don't use arrays. Instead, we make it easy to split into multiple rows so you can use regular SQL.
I haven't directly compared Clickhouse's all of different JSON treatments compared to what I've implemented, but my goal was to build something that you could run and would "just work the way it should."
Here's a more factual one:
- We don't use tuples for nested JSON. We just use underscores to show parent_child relationships in keys.
- We don't use arrays. Instead, we make it easy to split into multiple rows so you can use regular SQL.
I haven't directly compared Clickhouse's all of different JSON treatments compared to what I've implemented, but my goal was to build something that you could run and would "just work the way it should."