influxdb/iox_query/Cargo.toml

49 lines
1.7 KiB
TOML
Raw Normal View History

[package]
name = "iox_query"
description = "IOx Query Interface and Executor"
version.workspace = true
authors.workspace = true
edition.workspace = true
license.workspace = true
# This crate is designed to be independent of the rest of the IOx
# server and specific storage systems such as Mutable Buffer and Read Buffer.
#
# The rationale for this is to:
#
# 1. Keep change/compile/link time down during development when working on just this crate
# 2. Allow for query logic testing without bringing in all the storage systems.
[dependencies] # In alphabetical order
arrow = { workspace = true, features = ["prettyprint"] }
arrow_util = { path = "../arrow_util" }
async-trait = "0.1"
chrono = { version = "0.4", default-features = false }
feat: IOx InfluxQL planner learns how to process time range expressions (#6772) * feat: IOx learns InfluxQL time-range expression → DF logical Expr IOx now understand the how to evaluate an InfluxQL time-range filter expression and transform that to a DataFusion logical expression. * chore: move time range expression to independent functions There is no need for these to be part of the `InfluxQLToLogicalPlan` struct and makes them easier to test. * chore: support scalar now on either side of binary expression * chore: improve error messages * chore: address clippy concerns * chore: add tests for time ranges * chore: add a test where time appears on the right-hand side Ensure time is correctly identified on the right-hand side of a conditional expression. * chore: add tests that specify a timezone * chore: Run cargo hakari tasks * chore: fix linting issues * chore: Remove unnecessary line * chore: Feedback: Add API to parse a conditional expression Based on feedback from @alamb, we don't want to hide the error from parsing a `ConditionalExpression`. To do this, we use the public API, `parse_statements` as a model and provide a new API, `parse_conditional_expression`, which returns a `Result` with the error being a `ParseError`. Additionally, `ConditionalExpression` implements the `FromStr` API using the `parse_conditional_expression` API. * chore: PR feedback reverting this change I believe my intention was to update all instances in the match, but never completed the change. Will leave for another day. * chore: PR feedback add additional comments * chore: rustfmt --------- Co-authored-by: CircleCI[bot] <circleci@influxdata.com>
2023-02-01 00:27:17 +00:00
chrono-tz = { version = "0.8" }
2022-05-05 19:29:24 +00:00
data_types = { path = "../data_types" }
datafusion = { workspace = true }
datafusion_util = { path = "../datafusion_util" }
executor = { path = "../executor"}
futures = "0.3"
hashbrown = { workspace = true }
influxdb_influxql_parser = { path = "../influxdb_influxql_parser" }
itertools = "0.10.5"
once_cell = "1"
object_store = "0.5.4"
observability_deps = { path = "../observability_deps" }
parking_lot = "0.12"
parquet_file = { path = "../parquet_file" }
query_functions = { path = "../query_functions"}
regex = "1"
schema = { path = "../schema" }
2022-01-11 19:22:36 +00:00
snafu = "0.7"
tokio = { version = "1.25", features = ["macros", "parking_lot"] }
tokio-stream = "0.1"
trace = { path = "../trace" }
predicate = { path = "../predicate" }
workspace-hack = { path = "../workspace-hack"}
[dev-dependencies] # In alphabetical order
test_helpers = { path = "../test_helpers" }
assert_matches = "1"
insta = { version = "1", features = ["yaml"] }