andygrove opened a new pull request, #2570: URL: https://github.com/apache/datafusion-ballista/pull/2570
# Which issue does this PR close? No existing issue. # Rationale for this change \`DESCRIBE <table>\` produces a \`LogicalPlan::DescribeTable\`. \`BallistaQueryPlanner\` sent it to the scheduler as a general statement, but \`datafusion-proto\` cannot serialize that plan (\"LogicalPlan serde is not yet implemented for DescribeTable\"), so the statement could not be submitted. The plan already carries the table schema resolved from the client's catalog, so it does not need the cluster at all. # What changes are included in this PR? - \`BallistaQueryPlanner::create_physical_plan\` now plans \`DescribeTable\` with the local DataFusion planner, the same way it handles plans that only read \`information_schema\`. - A unit test in \`planner.rs\` checks that \`DESCRIBE\` is planned locally and does not become a \`DistributedQueryExec\`. - A client test in \`context_basic.rs\` runs \`DESCRIBE\` against a registered parquet table on a standalone context. # Are there any user-facing changes? \`DESCRIBE <table>\` now works from a Ballista \`SessionContext\`. There are no API changes. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
