-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ballista integration tests are failing #623
Comments
After improving the error message, this seems to be related to the recent support for qualified field names.
|
I am taking a look into this too. Sorry that I forgot to run integration tests from my local machine. Should we add integration test run in github action as well? |
It's my bad for not getting these test running in CI. We do have an issue open for that. apache/datafusion-ballista#24 |
I can take a stab at adding integration test to CI after this is fixed if no one gets to it :) After some initial investigation, I think this bug might have something to do with us not loading |
With #629, I am able to get the integration tests to pass for 1, 3, 5, 6. Looking at a different error with query 7 at the moment:
|
OK, I also disabled 7, 8, 9 in ballista integration test in #623. They were enabled in #55, but turns out other than adding qualified column support, there are more ser/de work needed (e.g. enable cross join serde). Most of those errors look straight forward to fix. I will send fixes as separate PRs. |
Describe the bug
When running
./dev/integration-tests.sh
I see:To Reproduce
Expected behavior
Queries should run without error.
Additional context
None
The text was updated successfully, but these errors were encountered: