Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement - manage sparse fact tables #484

Open
ThamaluM opened this issue Nov 30, 2019 · 0 comments
Open

Enhancement - manage sparse fact tables #484

ThamaluM opened this issue Nov 30, 2019 · 0 comments

Comments

@ThamaluM
Copy link

When the fact table is sparse (There are no facts for some dimension points) drilldown results do not contain the aggregates corresponding to dimension points which are not represented in fact table rows. (Those aggregations want to be represented as zeros)

Outer join the dimension table or the "detail method" will work but there is another problem. When there is a cut from another dimension these aggregates are missing again. (Due to WHERE condition rows added by outer join are ruled out because other columns are empty.)

Appropriate suggestion is to change cut parameters to Join condition ( for example a.dateid=b.id and b.product='PIZZA')

To implement this in a general way is hard. However it is better if we have this feature at least for time role. All cuts except time cuts come into the join condition and time cuts are in the where condition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant