Skip to content

update: remove time partition stream creation #1227

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

Merged

Conversation

nikhilsinhaparseable
Copy link
Contributor

@nikhilsinhaparseable nikhilsinhaparseable commented Mar 7, 2025

gives error if user tries to create a stream with a time partition
updating time partition limit is still allowed for older streams

Summary by CodeRabbit

  • Bug Fixes

    • Stream creation now returns a clear error when unsupported time partition options are provided.
  • Refactor

    • Simplified the validation and error handling process for stream creation, ensuring consistent responses when time partition inputs are used.

gives error if user tries to create a stream with a time partition
updating time partition limit is still allowed for older streams
Copy link
Contributor

coderabbitai bot commented Mar 7, 2025

Walkthrough

The pull request modifies error handling and control flow in the create_update_stream method within the Parseable struct. The previous implementation validated the time_partition_limit and computed a time_partition_in_days value. The updated implementation removes this conditional logic and instead returns a StreamError::Custom if either time_partition or time_partition_limit is provided, thereby disallowing time partitioning altogether.

Changes

File Changes
src/parseable/mod.rs Updated create_update_stream to immediately return a StreamError::Custom when time partition values are provided; removed conditional validation and the time_partition_in_days variable.

Sequence Diagram(s)

sequenceDiagram
    participant C as Client
    participant P as Parseable
    participant S as Stream Creator

    C->>P: create_update_stream(headers, body, stream_name)
    alt Time partition provided<br>(time_partition or limit non-empty)
        P-->>C: Return Error (BAD_REQUEST)
    else No time partition provided
        P->>S: create_stream(None, ...)
        S-->>P: Stream created
        P-->>C: Return created stream
    end
Loading

Possibly related PRs

Poem

I'm a rabbit with a hop and a skip,
Coding changes made my heart do a flip.
No more time partitions, the code now sings,
With clear errors and simplified things.
Hoppy leaps of joy, as bugs take a dip! 🐇
CodeRabbit cheers, with each little blip!


📜 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 533d9d2 and 181d189.

📒 Files selected for processing (1)
  • src/parseable/mod.rs (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/parseable/mod.rs
⏰ Context from checks skipped due to timeout of 90000ms (10)
  • GitHub Check: Build Default x86_64-pc-windows-msvc
  • GitHub Check: Build Default aarch64-apple-darwin
  • GitHub Check: Build Kafka aarch64-apple-darwin
  • GitHub Check: Build Kafka x86_64-unknown-linux-gnu
  • GitHub Check: Build Default x86_64-apple-darwin
  • GitHub Check: Build Default aarch64-unknown-linux-gnu
  • GitHub Check: Build Default x86_64-unknown-linux-gnu
  • GitHub Check: coverage
  • GitHub Check: Quest Smoke and Load Tests for Distributed deployments
  • GitHub Check: Quest Smoke and Load Tests for Standalone deployments

🪧 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.

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 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
src/parseable/mod.rs (1)

465-470: Consider removing redundant checks for time partitioning

Since creating streams with time partitioning is now completely disallowed (as enforced by lines 454-459), this check for both time partition and custom partition being set seems redundant.

-if !time_partition.is_empty() && custom_partition.is_some() {
-    return Err(StreamError::Custom {
-        msg: "Cannot set both time partition and custom partition".to_string(),
-        status: StatusCode::BAD_REQUEST,
-    });
-}
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7596825 and 533d9d2.

📒 Files selected for processing (1)
  • src/parseable/mod.rs (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (10)
  • GitHub Check: Build Default aarch64-apple-darwin
  • GitHub Check: Build Default x86_64-pc-windows-msvc
  • GitHub Check: Build Default x86_64-unknown-linux-gnu
  • GitHub Check: Build Default x86_64-apple-darwin
  • GitHub Check: Build Default aarch64-unknown-linux-gnu
  • GitHub Check: Build Kafka aarch64-apple-darwin
  • GitHub Check: Build Kafka x86_64-unknown-linux-gnu
  • GitHub Check: coverage
  • GitHub Check: Quest Smoke and Load Tests for Standalone deployments
  • GitHub Check: Quest Smoke and Load Tests for Distributed deployments
🔇 Additional comments (3)
src/parseable/mod.rs (3)

454-459: Implementation correctly blocks time partition creation

The added code block effectively implements the PR objective to remove the functionality for creating new streams with time partitions, while providing a clear error message to users.


483-483: Consistent change for time partition removal

Replacing the previous time partition value with None is consistent with the change to remove time partition functionality for new stream creation.


472-479:

❓ Verification inconclusive

Verify schema validation with time partition changes

The validate_static_schema function still accepts a time_partition parameter. Since time partition is no longer supported for new stream creation, make sure this doesn't cause issues.


🏁 Script executed:

#!/bin/bash
# Examine how validate_static_schema uses the time_partition parameter
ast-grep --pattern 'fn validate_static_schema($$$)' | grep -A 30 "validate_static_schema"

# Check if time_partition is used in convert_static_schema_to_arrow_schema
rg "convert_static_schema_to_arrow_schema" -A 2 -B 2

Length of output: 1246


Action Required: Revisit Time Partition Handling in Schema Validation

  • The function validate_static_schema in src/parseable/mod.rs still passes the time_partition parameter to convert_static_schema_to_arrow_schema (defined in src/static_schema.rs).
  • Since time partition is no longer supported for new stream creation, please verify that its continued use does not introduce unintended side effects. If the parameter is only relevant for legacy streams, consider conditionally bypassing or documenting its behavior for new stream scenarios.

coderabbitai[bot]
coderabbitai bot previously approved these changes Mar 7, 2025
@nitisht nitisht merged commit 10aef7b into parseablehq:main Mar 7, 2025
14 checks passed
de-sh pushed a commit to de-sh/parseable that referenced this pull request Mar 24, 2025
@coderabbitai coderabbitai bot mentioned this pull request Mar 24, 2025
3 tasks
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.

2 participants