So currently, we have f_player_season to summarize player-season-gametype level metrics... we also have d_player_team_season because we wanted to know player-season-team level stuff like is the player currently on the team, when did they join, etc...
But now... I'm thinking it was designed wrong... it should be f_player_team_season since this would give us the ability to drill down at the player-team-season level with all of the stuff created in d_player_team_season....
AC
Build f_player_team_season_season identically to f_player_season except with team_id (create and or update YML file)
Enahnce with the info from d_player_team_season (create and or update YML file)
Remove d_player_team_season
Re-engineer f_player_season to instead query from f_player_team_season (essentially dropping the team granularity, which only impacts those players who got traded
dmf95
commented
11 months ago
Brief
f_player_seasonto summarize player-season-gametype level metrics... we also haved_player_team_seasonbecause we wanted to know player-season-team level stuff like is the player currently on the team, when did they join, etc...f_player_team_seasonsince this would give us the ability to drill down at the player-team-season level with all of the stuff created in d_player_team_season....AC
f_player_team_season_season identically tof_player_seasonexcept with team_id (create and or update YML file)d_player_team_season(create and or update YML file)d_player_team_seasonf_player_seasonto instead query fromf_player_team_season(essentially dropping theteamgranularity, which only impacts those players who got traded