mirror of
https://github.com/apache/superset.git
synced 2024-09-12 00:29:39 -04:00
35 lines
1.4 KiB
ReStructuredText
35 lines
1.4 KiB
ReStructuredText
FAQ
|
|
===
|
|
|
|
|
|
Can I query/join multiple tables at one time?
|
|
---------------------------------------------
|
|
Not directly no. A Caravel SQLAlchemy datasource can only be a single table
|
|
or a view.
|
|
|
|
When working with tables, the solution would be to materialize
|
|
a table that contains all the fields needed for your analysis, most likely
|
|
through some scheduled batch process.
|
|
|
|
A view is a simple logical layer that abstract an arbitrary SQL queries as
|
|
a virtual table. This can allow you to join and union multiple tables, and
|
|
to apply some transformation using arbitrary SQL expressions. The limitation
|
|
there is your database performance as Caravel effectively will run a query
|
|
on top of your query (view). A good practice may be to limit yourself to
|
|
joining your main large table to one or many small tables only, and avoid
|
|
using ``GROUP BY`` where possible as Caravel will do its own ``GROUP BY`` and
|
|
doing the work twice might slow down performance.
|
|
|
|
Whether you use a table or a view, the important factor is whether your
|
|
database is fast enough to serve it in an interactive fashion to provide
|
|
a good user experience in Caravel.
|
|
|
|
|
|
How BIG can my data source be?
|
|
------------------------------
|
|
|
|
It can be gigantic! As mentioned above, the main criteria is whether your
|
|
database can execute queries and return results in a time frame that is
|
|
acceptable to your users. Many distributed databases out there can execute
|
|
queries that scan through terabytes in an interactive fashion.
|