Skip to content
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

CLI uses DataFusion context if no host or port are provided #219

Closed
andygrove opened this issue Sep 15, 2022 · 3 comments · Fixed by #252
Closed

CLI uses DataFusion context if no host or port are provided #219

andygrove opened this issue Sep 15, 2022 · 3 comments · Fixed by #252
Labels
bug Something isn't working

Comments

@andygrove
Copy link
Member

Describe the bug
The Ballista CLI executes queries against a DataFusion context, not Ballista, if no host and port are provided.

To Reproduce
☝️

Expected behavior
We should either remove this option or make it use Ballista in local mode.

Additional context
None

@andygrove andygrove added the bug Something isn't working label Sep 15, 2022
@r4ntix
Copy link
Contributor

r4ntix commented Sep 16, 2022

If the host and port parameter is not provided, do we use BallistaContext::standalone mode?

@andygrove
Copy link
Member Author

If the host and port parameter is not provided, do we use BallistaContext::standalone mode?

Yes, exactly.

@r4ntix
Copy link
Contributor

r4ntix commented Sep 17, 2022

If the host and port parameter is not provided, do we use BallistaContext::standalone mode?

Yes, exactly.

Ok, I will learn the CLI code and try to submit a PR for this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants