Influxdata
/
influxdb
mirror of https://github.com/influxdata/influxdb.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
influxdb/datafusion_util/Cargo.toml

20 lines
512 B
TOML
Raw Normal View History

refactor: explode arrow_deps (#1425) * refactor: explode arrow_deps * chore: workaround doctest bug
2021-05-05 16:59:12 +00:00
[package]
name = "datafusion_util"
version = "0.1.0"
authors = ["Andrew Lamb <andrew@nerdnetworks.org>"]
chore: use Rust edition 2021
2021-10-25 08:45:44 +00:00
edition = "2021"
refactor: explode arrow_deps (#1425) * refactor: explode arrow_deps * chore: workaround doctest bug
2021-05-05 16:59:12 +00:00
description = "Datafusion utilities"
[dependencies]
fix: ensure panic is propagated throw `AdapterStream` (#4980) Prior to this change background tasks that we feed into `AdapterStream` can panic but that would just end the stream without any user-visible error (except for the panic message on stdout/stderr). This was found while developing #4964. I have proposed another fix in #4966 but found that I actually developed an existing solution a 2nd time: `watch_task`. But I also see a major issue with the existing API: one can create `AdapterStream` with ordinary tokio tasks that are not watched at all, leaving the burden to the implementor to check for that (and actually we forgot that in `parquet_file`). So this change takes a slightly different approach: The `AdapterStream` does NOT accept ordinary join handles any longer but requires that you pass a "watched task". The newly introduced `WatchedTask` does the same as we did manually before: wrapping a future into a tokio task, watch it and wrap the watcher into a task. It is now way more difficult to do anything stupid (sure you can still mix up the tasks and the channels, but we need at least some flexibility here to allow for "split" and potential future fan-in/out constructs). Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2022-06-30 07:57:58 +00:00
async-trait = "0.1"
refactor: explode arrow_deps (#1425) * refactor: explode arrow_deps * chore: workaround doctest bug
2021-05-05 16:59:12 +00:00
datafusion = { path = "../datafusion" }
futures = "0.3"
fix: Move schema pivot work out of `execute` (#4520) * refactor: Extract watch_task into datafusion_util * refactor: do work in a separate task * fix: cleanup * fix: update test
2022-05-05 15:11:14 +00:00
observability_deps = { path = "../observability_deps" }
fix: ensure that query tokio background tasks are canceled (#4643) * fix: ensure that query tokio background tasks are canceled While I am not entirely sure if this explains some of the memory leaks I am seeing in prod, not canceling the tasks correctly certainly makes debugging way harder and also renders certain form of throttling (e.g. max. concurrent queries) somewhat ineffective. Note that parquet file downloads are currently NOT canceled because tokios `spawn_blocking` cannot be canceled. * refactor: `Vec` -> `Option` * refactor: `spawn_blocking` creates a join handle, even though it is useless Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2022-05-20 07:18:52 +00:00
pin-project = "1.0"
ci: fix (#5569) * ci: use same feature set in `build_dev` and `build_release` * ci: also enable unstable tokio for `build_dev` * chore: update tokio to 1.21 (to fix console-subscriber 0.1.8 * fix: "must use"
2022-09-06 14:13:28 +00:00
tokio = { version = "1.21", features = ["parking_lot", "sync"] }
fix: Use a consistent version range for tokio-stream across all crates
2021-12-02 21:13:11 +00:00
tokio-stream = "0.1"
feat: Results of running cargo hakari manage-deps
2021-11-19 14:21:57 +00:00
workspace-hack = { path = "../workspace-hack"}
fix: ensure panic is propagated throw `AdapterStream` (#4980) Prior to this change background tasks that we feed into `AdapterStream` can panic but that would just end the stream without any user-visible error (except for the panic message on stdout/stderr). This was found while developing #4964. I have proposed another fix in #4966 but found that I actually developed an existing solution a 2nd time: `watch_task`. But I also see a major issue with the existing API: one can create `AdapterStream` with ordinary tokio tasks that are not watched at all, leaving the burden to the implementor to check for that (and actually we forgot that in `parquet_file`). So this change takes a slightly different approach: The `AdapterStream` does NOT accept ordinary join handles any longer but requires that you pass a "watched task". The newly introduced `WatchedTask` does the same as we did manually before: wrapping a future into a tokio task, watch it and wrap the watcher into a task. It is now way more difficult to do anything stupid (sure you can still mix up the tasks and the channels, but we need at least some flexibility here to allow for "split" and potential future fan-in/out constructs). Co-authored-by: kodiakhq[bot] <49736102+kodiakhq[bot]@users.noreply.github.com>
2022-06-30 07:57:58 +00:00
[dev-dependencies]
schema = { path = "../schema" }