Cubes - Python Lightweight OLAP - 0.9 released(blog.databrewery.org)
blog.databrewery.org
Cubes - Python Lightweight OLAP - 0.9 released
http://blog.databrewery.org/post/23049114551/
4 comments
Interesting idea. Ofcourse, OLAP isn't just about the underlying cubes and dimensions, in the end it's about how the information is being presented to the user. There's a reason why Microsoft is so good at data warehousing, because their product is one of the best, and also extremely feature-rich from the "front end" to the back end.
well from my experience, working with OLAP Cubes, Microsoft is normally used when cost saving is important, its considered cheaper than competition. And the development tools are so easy to use, non-programmers can be trained to create and customize cubes.
On the front end, they only have excel, which is good, really good, but other tools have much simpler and in my opinion better clients, for example Cognos and BO
On the front end, they only have excel, which is good, really good, but other tools have much simpler and in my opinion better clients, for example Cognos and BO
You might want to look at OSS options like Pentaho, Jasper and Palo.
Palo (a competitor to Cognos TM1), in particular, is really nice. The other two leave a little to be desired on the UI side.
Palo (a competitor to Cognos TM1), in particular, is really nice. The other two leave a little to be desired on the UI side.
Excel is very familiar to many business users, and SSAS + Excel makes a powerful combo.
Currently I am working with a combination of PostgreSQL and Tableau, and find it a nicer environment to work with (coming from a MSSQL shop). I do not have the same automated aggregation engine supplied by SSAS, but Tableau in part makes up for that with visualization tools that require no coding on the UI side. I can focus my efforts on the data layer.
Currently I am working with a combination of PostgreSQL and Tableau, and find it a nicer environment to work with (coming from a MSSQL shop). I do not have the same automated aggregation engine supplied by SSAS, but Tableau in part makes up for that with visualization tools that require no coding on the UI side. I can focus my efforts on the data layer.
OLAP isn't just about the underlying cubes and dimensions, in the end it's about how the information is being presented to the user.
You are right. Cubes, dimensions and the logical model abstraction is the very first step: physical data implementation is hidden. Cubes is young, as mentioned in my comment - front-end helpers will be coming later. I will need some help on that part.
I am not quite sure about the "feature-richness". Yes, it might sell - in environments where people barely notice wrong data in 40-page monthly report, still being content about the report exhaustiveness. From my experience, many people want just basic stuff. I am trying to make cubes as small as possible (but not smaller), however extensible. For example, the cubes will not force you to use "cube's" way of drawing charts. It will provide few examples, based on common, accessible visualising backends. Along with the examples will have possibility to plug-in your own visualisation/reporting method.
The intention is not to create competitive product to the "big ones", it is rather to create light-weight, customizable alternative for many smaller projects.
Cubes aims (at this moment) rather for tool for tool creators than tool for end users. But you never know, how the wind will change... :-)
You are right. Cubes, dimensions and the logical model abstraction is the very first step: physical data implementation is hidden. Cubes is young, as mentioned in my comment - front-end helpers will be coming later. I will need some help on that part.
I am not quite sure about the "feature-richness". Yes, it might sell - in environments where people barely notice wrong data in 40-page monthly report, still being content about the report exhaustiveness. From my experience, many people want just basic stuff. I am trying to make cubes as small as possible (but not smaller), however extensible. For example, the cubes will not force you to use "cube's" way of drawing charts. It will provide few examples, based on common, accessible visualising backends. Along with the examples will have possibility to plug-in your own visualisation/reporting method.
The intention is not to create competitive product to the "big ones", it is rather to create light-weight, customizable alternative for many smaller projects.
Cubes aims (at this moment) rather for tool for tool creators than tool for end users. But you never know, how the wind will change... :-)
I haven't encountered a lot of BI nerds who are Pythonistas, but this is a great contribution nonetheless.
The more open source tools we can get that can begin displacing products like Cognos and BO, the better.
The more open source tools we can get that can begin displacing products like Cognos and BO, the better.
> BI nerds who are Pythonistas
One here. Very interested to see this project evolve.
One here. Very interested to see this project evolve.
Thank you, both. If you have any questions or suggestions, drop me a line or much better: discuss it on the cubes-discuss google group [1]. I would appreciate feedback from more experienced BI people than I am.
[1] https://groups.google.com/forum/?fromgroups#!forum/cubes-dis...
[1] https://groups.google.com/forum/?fromgroups#!forum/cubes-dis...
Is this going to integrate with the broader python ecosystem? I'm specifically wondering about packages like pyTables, pandas and larry.
I would love to and actually was looking at pyTables and little bit at pandas. I am coming from RDBMS-based DWH world mostly, so it is a bit new area to me, howerver from what I've learned so far, there is huge potential. Unfortunately, currently I have no resources to do that, even I would like to see that more than RDBS backends (as there are already plenty of tools for that). Is there any way how this possibility can be supported? I would not mind working on a project for someone that would require OLAP layer on top of something "strange" and that there will be (open-source) by-product in form of a backend...
[edit] p.s.: I am the only developer so far, and I am open for collaboration.
[edit] p.s.: I am the only developer so far, and I am open for collaboration.
Visualisation is not yet included and will be added in modular form of "presenters" [2]. If anyone with web/JS skills would like to help, he is welcome, as my skills in this area is little bit weak. There is unmaintained and unfinished prototype of JavaScript front-end as well [3]. Flask based example of simple dimension browsing is included in the source [4].
If you need any help with model creation, you encounter any issues, have a suggestion let me know.
[1] https://github.com/Stiivi/cubes/blob/master/examples/hello_w...
[2] https://github.com/Stiivi/cubes/issues/53
[3] https://github.com/stiivi/cubes.js
[4] https://github.com/Stiivi/cubes/tree/master/examples/sandbox...