8000
Skip to content

docs(spider): Remove legacy Spider integration doc. - #2436

Merged
LinZhihao-723 merged 5 commits into
y-scope:mainfrom
sitaowang1998:remove-legacy-doc
Jul 30, 2026
Merged

docs(spider): Remove legacy Spider integration doc.#2436
LinZhihao-723 merged 5 commits into
y-scope:mainfrom
sitaowang1998:remove-legacy-doc

Conversation

@sitaowang1998
@sitaowang1998 sitaowang1998 commented Jul 29, 2026
Copy link
Copy Markdown
Contributor

Description

This PR removes documentation for the legacy Spider integration in preparation for documenting the new Helm-based integration by:

  • Deleting the legacy “Using Spider with CLP” guide.
  • Removing its user documentation index card and toctree entry.
  • Removing Spider scheduler and compression-worker instructions from the Docker Compose deployment guide.
  • Removing legacy Spider services, dependencies, and deployment types from the deployment orchestration design doc.
  • Removing the outdated note stating that Spider is unavailable for Helm.

Checklist

  • The PR satisfies the contribution guidelines.
  • This is a breaking change and that has been indicated in the PR title, OR this isn't a
    breaking change.
  • Necessary docs have been updated, OR no docs need to be updated.

Validation performed

  • task docs:site built successfully.
  • Locally build doc served correctly, and searching of spider and Spider showed no result.
  • GitHub workflows pass.

Summary by CodeRabbit

  • Documentation
    • Updated deployment orchestration and architecture diagrams to reflect the current Celery-based long-running services.
    • Simplified “Deployment types” to cover only Base and Full configurations.
    • Updated multi-host Docker Compose startup instructions to remove optional Spider steps.
    • Removed the “Using Spider” guide and related landing page references.

@sitaowang1998
sitaowang1998 requested a review from a team as a code owner July 29, 2026 19:22
@coderabbitai
coderabbitai Bot commented Jul 29, 2026
Copy link
Copy Markdown
Contributor

Review Change Stack

Walkthrough

Spider services and deployment variants were removed from deployment architecture documentation, Docker Compose startup instructions, and user documentation navigation. The dedicated Spider usage guide was also deleted.

Changes

Spider documentation removal

Layer / File(s) Summary
Deployment architecture and configuration model
docs/src/dev-docs/design-deployment-orchestration.md
Architecture diagrams and service tables remove Spider components, while deployment types now cover Base and Full configurations using Presto or Celery query orchestration.
Compose startup and guide navigation
docs/src/user-docs/guides-docker-compose-deployment.md, docs/src/user-docs/index.md
Compose instructions remove Spider startup steps, and the Spider guide is removed from the documentation card grid and toctree.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: junhaoliao

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: removing legacy Spider integration documentation.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

Comment @coderabbitai help to get the list of available commands.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do have a docker-compose file for the legacy spider setup. We don't need to remove it in this PR, but we should probably make an issue to keep track of it for removal.

Comment on lines 242 to +252
### Deployment types

CLP supports multiple deployment configurations based on the compression scheduler and query engine.
CLP supports multiple deployment configurations based on the query engine.

| Deployment Type | Compression Scheduler | Query Engine |
|-----------------|-----------------------|------------------------------|
| Base | Celery | [Presto][presto-integration] |
| Full | Celery | Native |
| Spider Base | Spider | [Presto][presto-integration] |
| Spider Full | Spider | Native |

:::{note}
Spider support is not yet available for Helm.
:::

Docker Compose selects the appropriate compose file (e.g., `docker-compose.yaml` for Full,
`docker-compose-spider.yaml` for Spider Full) and uses `deploy.replicas` with environment
variables (e.g., `CLP_MCP_SERVER_ENABLED`) to toggle optional services. Helm uses conditional
templating to include/exclude resources.
Docker Compose uses `deploy.replicas` with environment variables (e.g., `CLP_MCP_SERVER_ENABLED`)
to toggle optional services. Helm uses conditional templating to include or exclude resources.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since there's only one type of compression scheduler now, shall we remove the "Compression Scheduler" column?
Depending on how we're gonna add the new Spider stuff, I will reword the table in a later PR.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since there's only one type of compression scheduler now, shall we remove the "Compression Scheduler" column?

i agree.

it might be easier to read today by turning the table into a simple list. e.g.,

CLP supports two deployment configurations, depending on the query engine:

  • Full: Uses Celery for query orchestration.
  • Base: Excludes the Celery-based orchestration in Full, to support the [Presto integration][presto-integration].

@@ -251,23 +241,15 @@ Services require persistent storage for logs, data, archives, and streams.

### Deployment types
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes in this section may require a sanity check from @junhaoliao.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@junhaoliao junhaoliao left a comment
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the rest lgtm

@LinZhihao-723 LinZhihao-723 changed the title docs: Remove legacy Spider integration doc. docs(spider): Remove legacy Spider integration doc. Jul 30, 2026
@LinZhihao-723 LinZhihao-723 left a comment
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Directly modified the PR title to include (spider).

Comment thread docs/src/dev-docs/design-deployment-orchestration.md Outdated
Co-authored-by: Lin Zhihao <59785146+LinZhihao-723@users.noreply.github.com>
@coderabbitai coderabbitai Bot left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/src/dev-docs/design-deployment-orchestration.md`:
- Around line 244-248: Decouple the documented Base/Full deployment models from
the shipped Compose stack: update the Compose configuration to remove or disable
spider-scheduler and spider-compression-worker, or explicitly document the
required Spider-specific Compose profile alongside the Helm deployment model.
Ensure the Base path no longer exposes unsupported Spider services by default.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e34d9d1e-aafc-496c-ace8-978c26bb5fc6

📥 Commits

Reviewing files that changed from the base of the PR and between d7df8c7 and 118de04.

📒 Files selected for processing (1)
  • docs/src/dev-docs/design-deployment-orchestration.md

Comment thread docs/src/dev-docs/design-deployment-orchestration.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

0