Conversation
…eservoir functionality
* fix: optimize slow queries on large datasets remove COUNT(*), use aggregates, reduce time windows, add caching * test: add comprehensive tests for platform timeline and active issues endpoints * add @logtide/reservoir, integrate in ingestion and query * Clickhouse engine, still to migrate most of the api * migrate all log queries to reservoir abstraction - add topValues, fromExclusive/toExclusive, getEngineType to reservoir - migrate query, alerts, dashboard, admin, retention, baseline, ingestion - conditional engine branching for continuous aggregates and drop_chunks - keep TimescaleDB aggregate fast paths, ClickHouse falls back to raw * fix getLogContext upper bound, add reservoir tests fix after query using new Date() as upper bound which excluded future-timestamped logs. add topValues and exclusive bounds tests for both clickhouse and timescale engines. * optimize reservoir engines, remove clickhouse-fdw - timescale: UNNEST insert, pg_trgm index, pool error handler, span_id index - clickhouse: PREWHERE, async_insert, ngrambf_v1, span_id index, IS NOT NULL parity - both: empty array validation, fromExclusive/toExclusive in count/distinct/topValues - remove redundant idx_project_time, remove LowCardinality on project_id * add Clickhouse support and update reservoir initialization logic * refactor query handling to use DateTime64 and improve token validation * refactor query handling to use DateTime64 and improve token validation * add span and trace operations to ClickHouse and Timescale tests * bump version to 0.6.1 and update CHANGELOG for ClickHouse support and performance improvements * refactor baseline-calculator to add type annotations for timeseries bucket processing * add reservoir tests to CI configuration and build steps * refactor test setup to ensure database existence before running tests * refactor ClickHouse integration tests to probe availability and skip if not ready * add reservoir package to Dockerfile and implement initial tests for reservoir functionality
… and resetting it afterward
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.