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

chore(doc) remove ballista from datafusion-cli readme #2604

Merged
merged 3 commits into from
May 24, 2022

Conversation

ming535
Copy link
Contributor

@ming535 ming535 commented May 24, 2022

Which issue does this PR close?

NONE

Rationale for this change

improve documentation

What changes are included in this PR?

  • remove ballista from datafusion-cli readme
  • build datafusion-cli and update Cargo.lock

Are there any user-facing changes?

no

Does this PR break compatibility with Ballista?

NA

@github-actions github-actions bot added the datafusion Changes in the datafusion crate label May 24, 2022
@waynexia
Copy link
Member

Thanks for this improvement. Could you please remove this paragraph https://github.com/apache/arrow-datafusion/blob/master/datafusion-cli/README.md#ballista as well. And I suppose the help text should also be update.

@alamb alamb added the documentation Improvements or additions to documentation label May 24, 2022
@alamb
Copy link
Contributor

alamb commented May 24, 2022

Thanks @ming535

@waynexia
Copy link
Member

https://github.com/apache/arrow-datafusion/pull/2604/files#diff-f8e712e7c585d2987696b343e70f216cb9695cf4c119c6a4035a030dff00eabbR40-R41

        --host <host>                Ballista scheduler host
        --port <port>                Ballista scheduler port

These are also outdated

@alamb
Copy link
Contributor

alamb commented May 24, 2022

Thanks @ming535 and @waynexia

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
datafusion Changes in the datafusion crate documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants