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
Fact missing data and facts listing a row per row linked to bridge table, is it the normal behaviour? #476
Comments
@brian-barba-hernandez It's very difficult to understand your problem. Better if you can provide the parts of your model that configure the dimension and the relevant joins. Add the result you got along with the expected results |
@ThamaluM Well, I can't provide the exact model due to an NDA but I can provide an example:
And the dimension is defined like this:
When querying the fact I don't get all keys and values, only one. |
I think I understood your problem. When bridge tables and dimension tables present final queries are performed on a joined table. When the tables joined it's the original table with repeat rows for each corresponding dimension values. Then what you got can be expected. I think this is the normal behavior. |
@ThamaluM Thanks for your response, I thought bridges would be handled differently to the dimensions when joining the tables. |
Hi there,
I recently started using the cubes library and it's been very useful so far. Aggregates are working as expected, I can get the results when slicing and cutting and the library behaves and performs nicely.
I'm using the slicer server under a docker container for testing purposes. Recently I have to turn a dimension having
hstore
into a key value model using a bridge for the multiple values.Aggregates keep working as expected but, when getting a single fact I only get a single row from the bridge, I guess it's because it only returns a "dimension.key" and "dimension.value" when I was expecting something like:
When listing facts I get the same fact several times and each one have a different "dimension.key" with the corresponding "dimension.value" depending on the volume in the bridge table.
I followed the instructions to join the bridges as stated in https://cubes.readthedocs.io/en/latest/schemas.html?highlight=bridge#many-to-many-relationship
Is that the normal behaviour due to some limitations or may I have something wrong?
The text was updated successfully, but these errors were encountered: