9514e290a2
* Upload static cohort using CSV, closes #2868 * fix tests * Fix tests * Fix e2e test * Avoid double inserts * Speed up query * Move to params * fix tests * initial cleanup * initial scaffold for cohort static logic * intiial frontend changes * initial working * fix error on iterable * stickiness people func refactor * Use JSON instead of protobuf * stickiness working * clickhouse route * unused import * move button * make interface easier to user * clickhouse support * restore cache decorator * endpoint adjustment * adjust how clickhouse handles inserting for static cohorts * split out processing into pg * use worker for clickhouse querying too * add pg test * ee test * add input for cohort naming * add stickiness test * condition for when to show save cohort * fix types * minor fix * remove repeats * remove hardcoded id * add date handling to trends cohort func * remove print * add link on success creation * cohort working * fix backend test * fix cohort typescript * remove unnecessary kafka topic * remove brackets * shift default * raise exceptions when debug or test is true * remove test flag * move trends insight related components to different folder * change get_earliest_timestamp * remove extraneous condition * fix test call * put behind ff * fix test x2 * fix tests * restore exceptions hog * fix tests * restore exceptions hog * fix test x20 Co-authored-by: Tim Glaser <tim@glsr.nl> |
||
|---|---|---|
| .. | ||
| migrations | ||
| models | ||
| queries | ||
| sql | ||
| test | ||
| views | ||
| __init__.py | ||
| client.py | ||
| demo.py | ||
| middleware.py | ||
| process_event.py | ||
| README.md | ||
| util.py | ||
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.
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.