Rework to modern Materialized Views

[mzealey]

• Move away from using inner MV's to separate MV and defined tables as per CH recommendations
• Switch all SummingMergeTree to AggregatingMergeTree to allow for more functionality in future if needed

[netlify]

✅ Deploy Preview for unrivaled-llama-9deaa9 canceled.

Name	Link
🔨 Latest commit	5b41c6b
🔍 Latest deploy log	https://app.netlify.com/sites/unrivaled-llama-9deaa9/deploys/6442925e3988f900083d10b4

[mosajjal]

looks good. I just tested it against some local data and it works. do you have any testing/benchmark on this? wondering if this is gonna affect the performance.

[mzealey]

There's no performance issue - it's just explicitly specifying the inner tablesOn 22 Apr 2023 08:03, Ali Mosajjal ***@***.***> wrote: looks good. I just tested it against some local data and it works. do you have any testing/benchmark on this? wondering if this is gonna affect the performance. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[dnsstub]

hi @mzealey

Move away from using inner MV's to separate MV and defined tables as per CH recommendations
it seems very much fine

`Switch all SummingMergeTree to AggregatingMergeTree to allow for more functionality in future if needed
can you please put some light over it because you are replacing every SummingMergeTree Instance with AggregatingMergeTree that doesnt seems to be efficient in every condition

`

[mzealey]

I've never seen a performance difference between Summing and Aggregating (with SimpleAggregationFunction), and Aggregating gives you so much more flexibility over extending function if you need.

[dnsstub]

i will post my comparisions here in 1 -2 days