distributed table (time_series_gin_dist) is not always used in cluster mode

metrico / qryn

Polyglot Observability Stack. Lightweight & Drop-in compatible with Loki, Prometheus, Tempo, Pyroscope, Opentelemetry, Datadog & more! WASM powered ⭐️ Star to Support

https://qryn.dev

GNU Affero General Public License v3.0

1.05k stars 63 forks source link

distributed table (time_series_gin_dist) is not always used in cluster mode #504

Closed R-omk closed 1 month ago

R-omk commented 1 month ago

https://github.com/metrico/qryn/blob/52d9c5dc20b32285726983970b6aba85b5cfe2f8/parser/registry/stream_selector_operator_registry/stream_selector_indexed_registry.js#L77

https://github.com/metrico/qryn/blob/52d9c5dc20b32285726983970b6aba85b5cfe2f8/promql/index.js#L106

akvlad commented 1 month ago

In this place time_series gin is used in a subrequest of the distributed table.

R-omk commented 1 month ago

ok, I see that there are other places where a distributed table joins a local one, if that’s how it’s intended and it’s correct, then close this ticket. I don't have any bug, it just seemed like logged query was wrong.

lmangani commented 1 month ago

Any question is a great question if it helps understand the underlying logic best. Thanks for opening and let us know if you notice any performance issue related to the current design.