You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Ballista context should get file metadata from scheduler, not from local disk #22
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
I have a Ballista cluster running, and each scheduler and executor has access to TPC-H data locally.
I am running the benchmark client on my desktop, and I do not have access to the data locally.
Query planning fails with "file not found" because BallistaContext::read_parquet is looking for the file on the local file system when it should be getting the file metadata from a scheduler in the cluster.
Describe the solution you'd like
The context should send a gRPC request to the scheduler to get the necessary metadata.
@andygrove as the client is handling the logical plan, I think it does not need to know about the list of files or the statistics, it only needs the schema:
with the current datafusion implementation, we could just build a table provider without any statistics on the client, and then load the statistics once the logical plan is deserialized on the scheduler (cost based optimizations would be ineffective on the client but that is not a big issue as we could run them on the scheduler instead)
Hi @andygrove, we have integrated ballista with HDFS support. Our workaround is to make the file path self described. For example, a local file path should be file://tmp/..., a hdfs file path should hdfs://localhost:xxx:/tmp/...
To make it work, we also changed the object store api a bit. Later I'll create a PR for this.
Activity
rdettai commentedon Sep 3, 2021
@andygrove as the client is handling the logical plan, I think it does not need to know about the list of files or the statistics, it only needs the schema:
As flight already has an endpoint to query the schema, this would avoid creating and maintaining a new one 😃
yahoNanJing commentedon Jan 29, 2022
Hi @andygrove, we have integrated ballista with HDFS support. Our workaround is to make the file path self described. For example, a local file path should be file://tmp/..., a hdfs file path should hdfs://localhost:xxx:/tmp/...
To make it work, we also changed the object store api a bit. Later I'll create a PR for this.
avantgardnerio commentedon Sep 1, 2022
@yahoNanJing this intersects work I'm currently working on, so anything you could share would be helpful!
milenkovicm commentedon Nov 17, 2026
closing as out of date