tustvold commented on code in PR #2226: URL: https://github.com/apache/arrow-datafusion/pull/2226#discussion_r856478974
########## datafusion/scheduler/Cargo.toml: ########## @@ -0,0 +1,57 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. + +[package] +name = "datafusion-scheduler" +description = "Scheduling for DataFusion query engine" +version = "7.0.0" +homepage = "https://github.com/apache/arrow-datafusion"; +repository = "https://github.com/apache/arrow-datafusion"; +readme = "../README.md" +authors = ["Apache Arrow <[email protected]>"] +license = "Apache-2.0" +keywords = ["arrow", "query", "sql"] +edition = "2021" +rust-version = "1.58" + +[lib] +name = "datafusion_scheduler" +path = "src/lib.rs" + +[features] + +[dependencies] +ahash = { version = "0.7", default-features = false } +arrow = { version = "12" } +async-trait = "0.1" +datafusion = { path = "../core", version = "7.0.0" } Review Comment: So, I'm not sure how to do this without introducing a circular dependency. Currently ExecutionPlan is defined in datafusion/core. Options I can see are: * Move ExecutionPlan into datafusion-common, this would require also moving the metrics * Merge datafusion-scheduler with datafusion/core I'm not sure which would be preferable? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
