trickstercache/trickster

https://github.com/questdb/questdb relies on changes in the v2.2 branch to access the pgwire and other postgres underpinnings. Support the PostgresQL endpoint / SQL syntax. requires a simple pre-parse clause hook, SAMPLE BY analyzer support and a few other dialect differences to work around prior to handing over to the cockroach parser update developer environment to run a QuestDB container and add a data seeder task container New branch for this work should be created from the repo's v2.2 branch, and PR will go into v2.2 instead of main. We'll merge v2.2 to main as we close out v2.1 bugfix. Logo is already in docs/images/external

https://github.com/greptimeteam/greptimedb relies on changes in the v2.2 branch to access the pgwire and other postgres underpinnings. Support the prometheus endpoint / PromQL. For this, the Trickster prometheus package should be adjusted for reuse by exposing a SupportedPaths() method that returns a deep clone of the prom paths, that GrepTimeDB can alter as needed (e.g., add new cache key inputs like db name, prepend paths for proper touting, etc.). Both prom and greptimedb's DefaultPathConfigs() can call SupportedPaths() so that everything uses the same source of truth. Support the PostgresQL endpoint / SQL syntax. Support the MySQL endpoint / SQL syntax. defer support for other protocols (gRPC, etc) proxy-only for non-TSDB HTTP endpoints like Jaeger and Loki update developer environment to run a GrepTimeDB all-in-one container and add a seeder task container New branch for this work should be created from the repo's v2.2 branch, and PR will go into v2.2 instead of main. We'll merg

IP Access Control Lists (ip_acls: named IPv4/IPv6 lists for listeners, backends and paths) Scope: a top-level ip_acls section of named network ACLs (addresses and CIDRs, v4 and v6); attachment by name to listeners, backends and paths; one core evaluator (an address in, a verdict out) used by the HTTP middleware, the stream (tcp/tls/udp) admission and an accept-time listener wrapper; reject or drop on denial; and a Kubernetes controller setting that puts generated backends behind an ACL. Branch from v2.2. Groundwork to read first The ACL builds on shared pieces that are in the tree and documented in docs/developer/flow-keys-and-admission.md. Read it before Phase 1. This plan names its sections rather than repeating them. Piece Where Developer doc section What the ACL uses it for Client addresses request.ClientIP (pkg/proxy/request), Flow.Client, clientip.ParseTrusted and clientip.Trusted (pkg/proxy/clientip) "Matching addresses" reading the address an ACL judges; the parsing conv

Rate Limiting (named limiters, request-attribute buckets, HTTP and stream listeners) Scope: a top-level rate_limiters section of named limiters; attachment by name to HTTP listeners, backends and paths; buckets keyed on configurable request attributes; enforcement on HTTP and, with the same core, on tcp/tls (new connections) and udp (sessions or datagrams) listeners; and a Kubernetes controller setting that puts generated backends behind a limiter. Branch from v2.2. Groundwork to read first The limiter builds on shared pieces that are in the tree and documented in docs/developer/flow-keys-and-admission.md. Read it before Phase 1. This plan names its sections rather than repeating them. Piece Where Developer doc section What the limiter uses it for Flow keys pkg/proxy/flowkey "Key sources", "Extractors", "Composite keys", "Hashing and the golden test" parsing keys, checking each key against the listener that reads it, reading bucket keys without allocating Key requirements flow