The version 2 of the activity schema introduced the feature_json, where you add all features into an object. That works significantly better. I usually take the approach of having a dimension table for each entity and join it when I prepare the tables in the presentation layer. That works well.
Hi Timo! Thanks for the video! My question is with just 3 columns for features, would it be enough in real world?
The version 2 of the activity schema introduced the feature_json, where you add all features into an object. That works significantly better. I usually take the approach of having a dimension table for each entity and join it when I prepare the tables in the presentation layer. That works well.