the "Object" data type works very well and is quite performant. But do note that if you have lots of "schemas" you will need to create multiple such columns that represent such columns e.g. one column each for GitHub,GitLab etc.
How would that look like? MatViews in CH are like insert triggers so does it mean that one MatView per schema?
>I see the only suboptimal part if different schemas have different types for the same field and it has to convert it to String.
Agree, this is what I was actually after and it actually happens with system data sometimes- you can have "user" field as an int and string in different schemas.
I see the only suboptimal part if different schemas have different types for the same field and it has to convert it to String.