kaushik-pankaj opened a new issue, #1058:
URL: https://github.com/apache/datafusion-ballista/issues/1058
**Describe the bug**
While running the TPC-H queries in distributed mode(having ballista-cli
pointing to ballista-scheduler, ballista-scheduler and one ballista-executor)
few queries are failing and few are getting passed.
Passed Queries - q1, q3, q4, q5, q6, q11, q12, q13, q16, q17, q19, q20, q21
Failed Queries - q2, q7, q8, q9, q10, q14, q15, q18, q22
Failed queries are giving similar error. For example, sharing one below for
query number 2.
`ballista_scheduler::scheduler_server::query_stage_scheduler] Failed to
update 1 task statuses for Executor 167eb7c2-fc0f-4232-a279-47aa0d0f70e7:
DataFusionError(Internal("PhysicalExpr Column references column 's_acctbal' at
index 9 (zero-based) but input schema only has 9 columns: [\"s_name\",
\"s_address\", \"s_nationkey\", \"s_phone\", \"s_acctbal\", \"s_comment\",
\"p_partkey\", \"p_mfgr\",
\"ps_supplycost\"]"))ballista_scheduler::scheduler_server::query_stage_scheduler]
Failed to update 1 task statuses for Executor
167eb7c2-fc0f-4232-a279-47aa0d0f70e7: DataFusionError(Internal("PhysicalExpr
Column references column 's_acctbal' at index 9 (zero-based) but input schema
only has 9 columns: [\"s_name\", \"s_address\", \"s_nationkey\", \"s_phone\",
\"s_acctbal\", \"s_comment\", \"p_partkey\", \"p_mfgr\", \"ps_supplycost\"]"))`
**To Reproduce**
Steps to reproduce the behavior:
1. check out the main branch.
2. do cargo build (build the project)
3. run scheduler and executor
4. connect ballista-cli to scheduler.
5. run TPC-H queries on ballista
cli(https://github.com/apache/datafusion-ballista/tree/main/benchmarks/queries)
**Expected behavior**
A clear and concise description of what you expected to happen.
**Additional context**
Things are working with datafusion version 35.0.0. As soon as we upgrade
datafusion version to 39.0.0, TPC-H queries start failing.
--
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]
