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

21 lines
555 B
TOML
Raw Normal View History

refactor: extract influxrpc, flight and testing gRPC out of influxdb_ioxd (#4106) * refactor: extract grpc service implementations out of influxdb_ioxd * chore: Run cargo hakari tasks * refactor: rename server_common to service_common * refactor: rename server_grpc_influxrpc to service_grpc_influxrpc * refactor: rename server_grpc_flight to service_grpc_flight * refactor: rename server_grpc_testing to service_grpc_testing * fix: Cargo.toml Co-authored-by: CircleCI[bot] <circleci@influxdata.com>
2022-03-23 20:14:45 +00:00
[package]
name = "service_common"
feat: Use workspace package metadata to reduce differences and repetition
2022-09-26 14:43:00 +00:00
version.workspace = true
authors.workspace = true
edition.workspace = true
license.workspace = true
refactor: extract influxrpc, flight and testing gRPC out of influxdb_ioxd (#4106) * refactor: extract grpc service implementations out of influxdb_ioxd * chore: Run cargo hakari tasks * refactor: rename server_common to service_common * refactor: rename server_grpc_influxrpc to service_grpc_influxrpc * refactor: rename server_grpc_flight to service_grpc_flight * refactor: rename server_grpc_testing to service_grpc_testing * fix: Cargo.toml Co-authored-by: CircleCI[bot] <circleci@influxdata.com>
2022-03-23 20:14:45 +00:00
feat: Use workspace dep inheritance for datafusion instead of shim crate
2022-10-24 17:47:45 +00:00
[dependencies] # In alphabetical order
chore(deps): Bump async-trait from 0.1.64 to 0.1.66 (#7129) Bumps [async-trait](https://github.com/dtolnay/async-trait) from 0.1.64 to 0.1.66. - [Release notes](https://github.com/dtolnay/async-trait/releases) - [Commits](https://github.com/dtolnay/async-trait/compare/0.1.64...0.1.66) --- updated-dependencies: - dependency-name: async-trait dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
2023-03-06 10:13:29 +00:00
async-trait = "0.1.66"
chore(deps): Bump bytes from 1.3.0 to 1.4.0 Bumps [bytes](https://github.com/tokio-rs/bytes) from 1.3.0 to 1.4.0. - [Release notes](https://github.com/tokio-rs/bytes/releases) - [Changelog](https://github.com/tokio-rs/bytes/blob/master/CHANGELOG.md) - [Commits](https://github.com/tokio-rs/bytes/compare/v1.3.0...v1.4.0) --- updated-dependencies: - dependency-name: bytes dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2023-02-01 00:30:56 +00:00
bytes = "1.4"
feat: Use workspace dep inheritance for datafusion instead of shim crate
2022-10-24 17:47:45 +00:00
datafusion = { workspace = true }
ci: fix cargo deny (#4629) * ci: fix cargo deny * chore: downgrade `socket2`, version 0.4.5 was yanked * chore: rename `query` to `iox_query` `query` is already taken on crates.io and yanked and I am getting tired of working around that.
2022-05-18 09:38:35 +00:00
iox_query = { path = "../iox_query" }
refactor: Move `flightsql` code into its own module, add docs and tests (#6640) * refactor: Move `flightsql` code into its own module * fix: get schema from LogicalPlan * refactor: use arrow_flight::sql::Any instead of prost_types::any * fix: cleanup docs and avoid as_ref * fix: Use Bytes * fix: use Any::pack * fix: doclink
2023-01-24 18:24:32 +00:00
flightsql = { path = "../flightsql" }
refactor: rework querier concurrency limiting (#4760) * refactor: rework querier concurrency limiting With #4752 we introduced a concurrency limit into the querier. It works by drawing permits from a central semaphore whenever we create a `QuerierNamespace`. This however only limits concurrency during query planning and not query execution, because the objects contained within the plan (chunks and some metadata) neither reference the permit nor the `QuerierNamespace`. Now one approach to fix that would be to wire up the permit all the down into all the query-related data structures. This however is very fiddly and potentially will get lost at some point, because as soon as we transform these data structures -- e.g. into streams -- the permit might get lost again. This will be potentially query-dependent and very hard to debug. So instead we reverse the approach and track the permits at the upper layer of the stack: the gRPC service entry points. There we also need to be careful -- e.g. when we return streams to tonic -- but it's way easier to review that then the deeply nested object hierarchy that is involved with queries. Also the separation of concerns is a bit clearer, because why would a "chunk" care about the "query concurrency" as a whole. * refactor: improve gRPC permit keeping and prepare tests
2022-06-02 09:49:58 +00:00
metric = { path = "../metric" }
parking_lot = "0.12"
feat: Use workspace dep inheritance for datafusion instead of shim crate
2022-10-24 17:47:45 +00:00
predicate = { path = "../predicate" }
tonic = "0.8"
feat: add tracing to instrumented semaphores (#5130) This will allow us to easily see how much time we spend during query processing waiting for the query semaphore. Ref #5129.
2022-07-15 07:50:28 +00:00
trace = { path = "../trace" }
feat: expose query semaphore metrics (#4836) The groundwork for that was already done, just needed a bit of wiring. This might help us to judge timeouts.
2022-06-13 09:36:50 +00:00
tracker = { path = "../tracker" }
chore: Rerun cargo hakari manage-deps
2023-02-24 18:02:23 +00:00
workspace-hack = { version = "0.1", path = "../workspace-hack" }