When diving into cubes i was asking myself, which source code is the one i download when running pip install cubes[mongo]? Is this now the official repo of the mongodb store cubes backend?
It would be nice if someone could provide some clarification about the state of https://github.com/DataBrewery/cubes/issues/252 and maybe some words on the current functionality when employing mongodb collections as a cube store.
It looks like there is probably some interest in contributing to it (see, for example @miraculixx pull request) but i looking at the issues and repos, we might need some kind of clarification about the correct repo to use and possibly some info on the state or functionality of this mongodb storage adapter in cubes. For example, the current cubes milestone is called 1.1 Back to SQL but i couldn't find some information and insights on why this is so and what thoughts led to the decision.
If this is the repo for the cubes-mongodb store then i think we could make this clear and migrate the issues mentioned in the cubes package to here. I am just asking because i ran into the https://github.com/DataBrewery/cubes/issues/257 issue yesterday and was able to fix it myself through using hints in the comments mentioned by @hmarrao - and it would be nice if others coming after us would not need to go after that.
When diving into cubes i was asking myself, which source code is the one i download when running
pip install cubes[mongo]? Is this now the official repo of the mongodb store cubes backend?It would be nice if someone could provide some clarification about the state of https://github.com/DataBrewery/cubes/issues/252 and maybe some words on the current functionality when employing mongodb collections as a cube store.
It looks like there is probably some interest in contributing to it (see, for example @miraculixx pull request) but i looking at the issues and repos, we might need some kind of clarification about the correct repo to use and possibly some info on the state or functionality of this mongodb storage adapter in cubes. For example, the current cubes milestone is called 1.1 Back to SQL but i couldn't find some information and insights on why this is so and what thoughts led to the decision.
If this is the repo for the cubes-mongodb store then i think we could make this clear and migrate the issues mentioned in the cubes package to here. I am just asking because i ran into the https://github.com/DataBrewery/cubes/issues/257 issue yesterday and was able to fix it myself through using hints in the comments mentioned by @hmarrao - and it would be nice if others coming after us would not need to go after that.
Other purely cubes-mongo related issues currently tracked on the cubes repo might be: https://github.com/DataBrewery/cubes/issues/315 and https://github.com/DataBrewery/cubes/issues/336
Thanks for and clarification and your support!