If you look up a single blob by id, you're going to have a bad time.
My experience comes from using CH as an secondary store for relational data where it could be filtered, sorted and aggregated much faster. The downside was that pulling out all the columns resulted in poor performance - like I said, it was just as slow as a relational store when doing a SELECT *.
Comments
If you look up a single blob by id, you're going to have a bad time.
My experience comes from using CH as an secondary store for relational data where it could be filtered, sorted and aggregated much faster. The downside was that pulling out all the columns resulted in poor performance - like I said, it was just as slow as a relational store when doing a SELECT *.
This is impossible. I suggest reading through CH's json functions and seeing how they combine with materialized views.
ex: https://eng.uber.com/logging/