docs(sql): Mark Ballista as an experimental feature

[chenquan]

Summary by CodeRabbit

• Documentation
  • Updated the SQL input component documentation to clearly mark the "ballista" section as experimental.
  • Added a new "ballista (experimental)" configuration section to the SQL processor documentation, describing how to enable distributed SQL execution with Ballista.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The documentation for the SQL input and processor components was updated to clarify the experimental status of Ballista integration. The SQL input documentation now marks the Ballista section as experimental, while the SQL processor documentation adds a new "ballista (experimental)" configuration section detailing distributed query execution via Ballista.

Changes

File(s)	Change Summary
docs/docs/components/0-inputs/sql.md	Updated the "ballista" configuration section heading to "ballista (experimental)" to mark it as experimental.
docs/docs/components/2-processors/sql.md	Added a new optional "ballista (experimental)" configuration section, describing distributed query execution via Ballista with a required remote_url property.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant SQL Processor
    participant Ballista Server

    User->>SQL Processor: Submit SQL query with "ballista (experimental)" config
    SQL Processor->>Ballista Server: Send query to remote_url
    Ballista Server-->>SQL Processor: Return distributed execution results
    SQL Processor-->>User: Provide query results

Loading

Poem

In docs we mark, with gentle cheer,
Ballista’s path—experimental, clear!
Distributed queries now take flight,
Across the docs, both day and night.
With every hop and every bound,
New features in the docs are found!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f5dbc85 and 6f929a8.

📒 Files selected for processing (2)

• docs/docs/components/0-inputs/sql.md (1 hunks)
• docs/docs/components/2-processors/sql.md (1 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.