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
I am testing Ballista with DataFusion 33 and getting this confusing error:
File 'supplier.parquet' does not match the expected extension '.parquet'
I am pretty sure that supplier.parquet does end with .parquet.
Here is the code that produces this error message:
let file_name = path.prefix().filename().unwrap_or_default();if !path.as_str().ends_with(&option_extension) && file_name.contains('.'){returnexec_err!("File '{file_name}' does not match the expected extension '{option_extension}'");}
The code checks to see if path.as_str() ends with the extension, but the error message shows file_name instead of path.as_str(), so this seems to be misleading. I think it would be better to also show the value of path.as_str() in the error message to make this easier to debug.
I also wonder whether it is intentional that we are checking path.as_str() rather than file_name?
To Reproduce
This is not easy to reproduce via Ballista.
Expected behavior
I expect the error message to give me all of the context necessary so that I can debug the issue (which may well be due to a Ballista bug in this case).
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
I am testing Ballista with DataFusion 33 and getting this confusing error:
I am pretty sure that
supplier.parquet
does end with.parquet
.Here is the code that produces this error message:
The code checks to see if
path.as_str()
ends with the extension, but the error message showsfile_name
instead ofpath.as_str()
, so this seems to be misleading. I think it would be better to also show the value ofpath.as_str()
in the error message to make this easier to debug.I also wonder whether it is intentional that we are checking
path.as_str()
rather thanfile_name
?To Reproduce
This is not easy to reproduce via Ballista.
Expected behavior
I expect the error message to give me all of the context necessary so that I can debug the issue (which may well be due to a Ballista bug in this case).
Additional context
No response
The text was updated successfully, but these errors were encountered: