Open MasaNahti opened 2 years ago
If you are interested in working on this issue, please leave a comment below and we will be happy to assign the issue to you. If this is the first time you are contributing a Pull Request to Cube.js, please check our contribution guidelines. You can also post any questions while contributing in the #contributors channel in the Cube.js Slack.
Describe the bug I am using Cube.js with Docker in dev mode and testing it with our Oracle 12c database. In Cube.js Playground, I use "Add Rollup to Schema" to define PreAggregations. After defining a PreAggregation like this, I run a query in the Playground that should hit PreAggregations. According to Cube logs, it does, but then it breaks with this issue which is also displayed in Playground:
ORA-01036: illegal variable name/number
Logs are huge and confusing, so I will just copy the error and its traceback:
To Reproduce Steps to reproduce the behavior:
Expected behavior Working preAggregations with Oracle database.
Minimally reproducible Cube Schema I didn't understand this part of the issue instruction so I am just copying an example of my data schema:
Version: Cube.js (0.29.34), ran in a Docker container from an image built from my custom dev.Dockerfile (in order to solve this open issue)
Additional context I get the same error whether I do mess with Cube code and fix this issue or not. If I do the fix, a certain query will work if I have no PreAggregations defined. That means that querying the Oracle database in the background works. But after I "Add Rollup to Schema", for this same query I get the error above. That makes me think that when building PreAggregations there is some other query to Oracle database that Oracle does not like. Or, querying the PreAggregation tables can also signal ORA errors. The same issue happens whether I use partitions or not. Cube Store (in dev mode) is running. My only modification in the
cube.js
file is:Though I am not using the ungrouped property for testing PreAggregations. I should mention that I get the same error if I use Postman for querying Cube as well.
I really wished to fix this by myself but it is just far out of my league.