Publish tdigest library

TimescaleDB and PostgreSQL
1

Hi Timescale! I’m trying to use your timescaledb-toolkit’s tdigest support. It’s cool, but I need to send tdigests from my client. Each of my servers does over 80,000 requests per second at peak, and that’s unrealistic to aggregate in postgres on ingest with scores of servers.

I see you have a library for this use: timescaledb-toolkit/crates/t-digest at main · timescale/timescaledb-toolkit · GitHub

In this change, I see you’re adding experimental support. I imagine in the intervening 2 and a half years your repo strategy has seen some iteration? This old issue seems to have stalled.

I realize I can do git submodules, or manually copy the needful code - but that’s a stopgap and will make updates painful. What’s the realistic outlook for you to add something in your github release action like

    - uses: katyo/publish-crates@v2
      with:
          registry-token: ${{ secrets.CARGO_REGISTRY_TOKEN }}

I will work around this missing package support for now, but I’d love to avoid writing poor update automation to approximate what the cargo package system already does well!

2

For clarity and anyone else reading, the easiest way to work around this for now is something like this in Cargo.toml:

tdigest = { git = "https://github.com/timescale/timescaledb-toolkit.git" }

It’s a fine workaround but it’s missing out on versioning and normal documentation discoverability.