Queries with granularity result in incomplete data when date range is not aligned with granularity and pre-aggregations are activated

[gizmodus]

Describe the bug
When sending a query with a start date that is not aligned with the specified granularity, the server does not send data of "incomplete" time partitions. This problem only appears when pre-aggregations are activated. If pre-aggregations are deactivated, the results are as expected.
Example: When a query with date range 21/04/2019 - 21/05/2019 and granularity "month" is sent, the server only returns data of May and data of April is missing.

To Reproduce
Steps to reproduce the behavior:

1. Activate rollup pre-aggregations and send a query with a start date that is not aligned with granularity.
2. The server only returns data of the complete weeks / months / years.

Expected behavior
The server should respond with the same data no matter whether pre-aggregations are activated or not.

Version:
@cubejs-backend/server-core: 0.8.6

[paveltiunov]

@gizmodus Hey Reto! Thanks for posting this. I can confirm this behavior. There're multiple options to solve this. Strict one is to do not match rollup with monthly granularity if date range is not aligned. But in order to save all performance benefits we'd need to implement daily granularity match to monthly ones first.

[gizmodus]

@paveltiunov Are there any news on this?

In my opinion, this issue is quite important. See screenshot below:
Results only appear for 20.03.2020 if the date filter is set to the 21.03.2020 otherwise it just stays empty.

[paveltiunov]

@gizmodus Hey Reto! Are you using partitionGranularity? If so this one should be fixed. Could you please check?

[gizmodus]

@paveltiunov We updated cube.js from 0.12.2 to 0.17.0 and the problem seems to have been fixed in the meantime. So it is working as expected now without any changes on the configuration side. Thanks for your support!