https://github.com/paoliniluis/metabase-cube

Working demo of Metabase and Cube
https://github.com/paoliniluis/metabase-cube

Last synced: 7 days ago
JSON representation

Working demo of Metabase and Cube

• Host: GitHub
• URL: https://github.com/paoliniluis/metabase-cube
• Owner: paoliniluis
• Created: 2022-12-05T17:14:39.000Z (about 2 years ago)
• Default Branch: main
• Last Pushed: 2023-08-30T18:11:19.000Z (over 1 year ago)
• Last Synced: 2024-11-07T06:47:33.808Z (about 2 months ago)
• Language: JavaScript
• Size: 224 KB
• Stars: 1
• Watchers: 1
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# metabase-cube

Working demo of Metabase and Cube with 3 use cases that are elegantly solved by using both tools

## Data isolation

In Metabase, Data Sources are tied to questions 1:1, so if you have data isolated per schema or database, you can't use Metabase sandboxing. With Cube, you can use sandboxing and still keep the data isolated via schemas, databases or engines, as Cube will act as the connection broker sending the user to the data source it belongs to

![Data isolation use case](Isolation.png)

## Partitioned tables

If you're using a Data Lake, then you know how expensive it is to query it without using a WHERE clause. Cube allows you to inject SQL statatements on the fly with the user permissions that come from Metabase.

![Partitioned tables use case](partitioning.png)

## Tiered cachng

In Metabase, you can use App level caching at question or dashboard level, but this might not be sufficient for many users. Cube allows you to do pre-aggregations that will be cached on Cube Store so the queries will never reach the Data Warehouse

![Tiered caching use case](tiered-caching.png)