mirrors/posthog
0
0
Fork 0
mirror of https://github.com/PostHog/posthog.git synced 2024-12-01 04:12:23 +01:00
Code Issues Releases Activity
616c25ef00
posthog/ee/clickhouse
History
James Greenhill 616c25ef00
Add support for CH for instance status reports (#5980) 
* Add support for CH for instance status reports

* format

* `BETWEEN` a rock and a hard place
2021-09-15 18:39:09 -07:00
..
bin Clickhouse flamegraphs (#5752) 2021-09-08 16:24:44 +03:00
materialized_columns Make marking materialized columns as MATERIALIZED stateless (#5831) 2021-09-07 11:53:57 +00:00
migrations Migrate person_distinct_id table to CollapsingMergeTree (#5563) 2021-08-18 17:25:02 +03:00
models Add support for CH for instance status reports (#5980) 2021-09-15 18:39:09 -07:00
queries Fix IndexError in Retention endpoint: do not fail if there is more data than expected from clickhouse query (#5892) 2021-09-14 10:38:40 +01:00
sql Bugfix: cohort calculating race condition (#5929) 2021-09-14 08:33:43 +02:00
test Generate clickhouse query error class dynamically (#5492) 2021-08-06 16:31:42 +01:00
views Swap out old paths querying class with new 2 (#5887) 2021-09-10 15:38:45 -04:00
__init__.py
client.py Improve clickhouse flamegraphs (#5874) 2021-09-09 12:40:46 +00: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 Clickhouse flamegraphs (#5752) 2021-09-08 16:24:44 +03:00
timer.py Make timer safe (#5469) 2021-08-05 16:58:21 +03:00
util.py Speed up EE tests by not destroying tables (#5715) 2021-08-25 10:58:09 +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.