chore: remove pmeta ingestion from OSS

[nikhilsinhaparseable]

Summary by CodeRabbit

• Refactor
  • Simplified startup sequence by removing cluster metrics scheduler initialization and streamlining internal hot-tier push steps while preserving hot-tier metadata initialization and S3 download during startup.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Startup in the query server handler was simplified: removal of cluster metrics scheduler initialization and its log, and removal of an internal hot-tier push; hot-tier metadata initialization and S3 download remain unchanged. (50 words)

Changes

Cohort / File(s)	Summary
Query Server Init Simplification src/handlers/http/modal/query_server.rs	Removed init_cluster_metrics_schedular import and call, removed tracing::info import and scheduler-start log, and removed hot_tier_manager.put_internal_stream_hot_tier().await? during startup. Preserved initialize_hot_tier_metadata_on_startup and download_from_s3 steps.

Sequence Diagram(s)

sequenceDiagram
    participant QS as QueryServer
    participant Hot as HotTierManager
    participant Cluster as ClusterModule
    participant S3 as S3

    rect rgb(230, 248, 255)
    Note over QS: Original startup (before)
    QS->>Cluster: init_cluster_metrics_schedular()
    Cluster-->>QS: ack
    QS->>Hot: put_internal_stream_hot_tier().await?
    Hot-->>QS: ack
    end

    rect rgb(240, 240, 240)
    Note over QS: New startup (after)
    QS->>Hot: initialize_hot_tier_metadata_on_startup()
    Hot-->>QS: ack
    QS->>S3: download_from_s3()
    S3-->>QS: data
    end

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Review cluster module imports/usages to ensure scheduler removal doesn't leave unmet dependencies.
• Verify hot tier startup sequence in HotTierManager for any implicit assumptions about the removed internal push.

Poem

🐰 I hopped through code at morning light,
Removed a log, made startup light,
No scheduler fuss, no extra shove,
Hot tiers wake with gentle love,
A quiet patch — a rabbit's delight!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided by the author, but the template requires a description section with details about the goal, rationale, key changes, and testing checklist.	Add a description following the template with sections for: the goal of this PR, rationale for changes, key changes made, and complete the testing/documentation checklist items.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: remove pmeta ingestion from OSS' accurately summarizes the main change—removing pmeta (cluster metrics scheduler and internal hot-tier push) from OSS initialization.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 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 e93e834 and d85ecf8.

📒 Files selected for processing (1)

• src/handlers/http/modal/query_server.rs (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/handlers/http/modal/query_server.rs

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (10)

• GitHub Check: coverage
• GitHub Check: Build Default x86_64-unknown-linux-gnu
• GitHub Check: Build Default aarch64-apple-darwin
• GitHub Check: Build Default x86_64-apple-darwin
• GitHub Check: Build Default x86_64-pc-windows-msvc
• GitHub Check: Build Default aarch64-unknown-linux-gnu
• GitHub Check: Build Kafka x86_64-unknown-linux-gnu
• GitHub Check: Build Kafka aarch64-apple-darwin
• GitHub Check: Quest Smoke and Load Tests for Distributed deployments
• GitHub Check: Quest Smoke and Load Tests for Standalone deployments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}