mirrors/posthog
0
0
Fork 0
mirror of https://github.com/PostHog/posthog.git synced 2024-11-28 09:16:49 +01:00
Code Issues Releases Activity
82352c4a62
posthog/ee/clickhouse
History
Neil Kakkar 82352c4a62
Funnel Groups filtering (#6940) 
* enable groups filtering

* rerun snapshots

* update team

* fix tests
2021-11-09 08:32:55 +00:00
..
bin Clickhouse flamegraphs (#5752) 2021-09-08 16:24:44 +03:00
materialized_columns Groups: Use materialized columns for groups (#6938) 2021-11-08 15:49:39 +02:00
migrations Ingest window_id for recordings (#6806) 2021-11-08 14:29:54 -08:00
models Funnel Groups filtering (#6940) 2021-11-09 08:32:55 +00:00
queries Funnel Groups filtering (#6940) 2021-11-09 08:32:55 +00:00
sql Ingest window_id for recordings (#6806) 2021-11-08 14:29:54 -08:00
test Migrate event-related logics to be project-based (#6566) 2021-10-22 18:32:58 +02:00
views WIP: Groups FE filtering (#6764) 2021-11-05 10:21:28 -04:00
__init__.py
client.py Make PRINT_SQL output readable (#6245) 2021-10-05 11:27:17 +03:00
demo.py Populate a lone session recording for demo (#3128) 2021-01-29 14:28:55 +01:00
errors.py Generate clickhouse query error class dynamically (#5492) 2021-08-06 16:31:42 +01:00
generate_local.py Generate local tests cases (#4874) 2021-06-25 12:38:04 -04:00
middleware.py Move is_clickhouse_enabled from posthog.ee to posthog.utils (#5902) 2021-09-11 01:43:24 +02:00
README.md Add --plan and --fake flags to migrate_clickhouse (#4160) 2021-04-29 15:40:12 +03:00
system_status.py Add events count to system status page (#6062) 2021-09-21 22:48:32 +00:00
timer.py Make timer safe (#5469) 2021-08-05 16:58:21 +03:00
util.py BE (Groups/Trends): Testing follow-up PR (#6923) 2021-11-08 10:52:10 +02:00

README.md

Clickhouse Support (Enterprise Feature)

To accomodate high volume deployments, Posthog can use Clickhouse instead of Postgres. Clickhouse isn't used by default because Postgres is easier to deploy and maintain on smaller instances and on platforms such as Heroku.

Clickhouse Support works by swapping in separate queries and classes in the system for models that are most impacted by high volume usage (ex: events and actions).

Migrations and Models

The django_clickhouse orm is used to manage migrations and models. The ORM is used to mimic the django model and migration structure in the main folder.

Certain migrations (e.g. changing table engines) can be quite expensive and tricky, especially for deployments outside of cloud. To skip these steps during deployment setup, check for the CLICKHOUSE_INITIAL_MIGRATIONS environment variable.

If you need help in making them happen, ask for help from team deployments.

Queries

Queries parallel the queries folder in the main folder however, clickhouse queries are written in SQL and do not utilize the ORM.

Tests

The tests are inherited from the main folder. The Clickhouse query classes are based off BaseQuery so their run function should work just as the Django ORM backed query classes. These classes are called with the paramterized tests declared in the main folder which allows the same suite of tests to be run with different implementations.

Views

Views contain Viewset classes that are not backed by models. Instead the views query Clickhouse tables using SQL. These views match the interface provide by the views in the main folder.