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

feat(fuzz): add alter table options for alter fuzzer #5074

Merged
merged 15 commits into from
Dec 12, 2024

Conversation

CookiePieWw
Copy link
Collaborator

@CookiePieWw CookiePieWw commented Nov 29, 2024

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

What's changed and what's your intention?

As title. Also move some files for clearer structure.

Currently there's no validation for the alter table option stmt, just add them to the fuzzer.

Checklist

  • I have written the necessary rustdoc comments.
  • I have added the necessary unit tests and integration tests.
  • This PR requires documentation updates.

@CookiePieWw CookiePieWw requested a review from a team as a code owner November 29, 2024 08:47
Copy link
Contributor

coderabbitai bot commented Nov 29, 2024

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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. (Experiment)
  • @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.

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.

@github-actions github-actions bot added the docs-not-required This change does not impact docs. label Nov 29, 2024
Copy link

codecov bot commented Nov 29, 2024

Codecov Report

Attention: Patch coverage is 86.18267% with 59 lines in your changes missing coverage. Please review.

Project coverage is 83.77%. Comparing base (b35221c) to head (adaa9c3).
Report is 19 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5074      +/-   ##
==========================================
- Coverage   84.05%   83.77%   -0.29%     
==========================================
  Files        1168     1171       +3     
  Lines      217373   217925     +552     
==========================================
- Hits       182718   182561     -157     
- Misses      34655    35364     +709     

@fengjiachun fengjiachun requested a review from WenyXu December 2, 2024 07:20
@WenyXu
Copy link
Member

WenyXu commented Dec 2, 2024

I think we need to verify table options after alterations.

@CookiePieWw
Copy link
Collaborator Author

CookiePieWw commented Dec 2, 2024

I think we need to verify table options after alterations.

Agree. We can add a table validator like row/column validator. The column types/names can be validated in validator as well.

@WenyXu
Copy link
Member

WenyXu commented Dec 2, 2024

I think we need to verify table options after alterations.

Agree. We can add a table validator like row/column validator. The column types/names can be validated in validator as well.

Do you have plans to add it?

@CookiePieWw
Copy link
Collaborator Author

Do you have plans to add it?

Sure, I'll add it later.

@CookiePieWw
Copy link
Collaborator Author

Updated with a table option validator, ptal :) @WenyXu

Copy link
Member

@WenyXu WenyXu left a comment

Choose a reason for hiding this comment

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

LGTM

@WenyXu WenyXu enabled auto-merge December 5, 2024 09:38
tests-fuzz/src/context.rs Outdated Show resolved Hide resolved
tests-fuzz/src/translator/postgres/alter_expr.rs Outdated Show resolved Hide resolved
tests-fuzz/src/generator/alter_expr.rs Outdated Show resolved Hide resolved
tests-fuzz/targets/ddl/fuzz_alter_table.rs Outdated Show resolved Hide resolved
tests-fuzz/src/validator/table.rs Outdated Show resolved Hide resolved
tests-fuzz/src/validator/table.rs Outdated Show resolved Hide resolved
@CookiePieWw
Copy link
Collaborator Author

Updated with new ttl options, PTAL :) @WenyXu @evenyag

@WenyXu WenyXu added this pull request to the merge queue Dec 12, 2024
Merged via the queue into GreptimeTeam:main with commit 03ad6e2 Dec 12, 2024
36 checks passed
evenyag pushed a commit that referenced this pull request Dec 20, 2024
* feat(fuzz): add set table options to alter fuzzer

* chore: clippy is happy, I'm sad

* chore: happy ci happy

* fix: unit test

* feat(fuzz): add unset table options to alter fuzzer

* fix: unit test

* feat(fuzz): add table option validator

* fix: make clippy happy

* chore: add comments

* chore: apply review comments

* fix: unit test

* feat(fuzz): add more ttl options

* fix: #5108

* chore: add comments

* chore: add comments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-not-required This change does not impact docs.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants