80a699ef4e
* convert sessions table logic to TS * convert rest of sessions to TS * sessions table logic refactor, store date in the url * add back/forward buttons * load sessions based on the URL, not after mount --> avoids duplicate query if opening an url with a filter * prevent multiple queries * throw error if failed instead of returning an empty list * date from filters * rename offset to nextOffset * initial limit/offset block * indent sql * support limit + offset * load LIMIT+1 sessions in postgres, pop last and show load more sign. (was: show sign if exactly LIMIT fetched) * based offset is always 0 * default limit to 50 * events in clickhouse sessions * add elements to query results * add person properties to sessions query response * show seconds with two digits * fix pagination, timestamp calculation and ordering on pages 2 and beyond * mypy * fix test * add default time to fix test, fix some any(*) filter issues * remove reverse * fix mypy error, indent SQL * add pagination test for postgres * Run insight API tests in Clickhouse Co-authored-by: Eric <eeoneric@gmail.com> |
||
|---|---|---|
| .. | ||
| migrations | ||
| models | ||
| queries | ||
| sql | ||
| test | ||
| views | ||
| __init__.py | ||
| clickhouse_test_runner.py | ||
| client.py | ||
| demo.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.