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

fix(meta): fix & enable e2e tests with MySQL meta backend #19846

Merged
merged 6 commits into from
Dec 23, 2024

Conversation

BugenZhao
Copy link
Member

Signed-off-by: Bugen Zhao [email protected]I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

Follow up of #19595. Address bugs for MySQL meta backend and re-enable it.

Checklist

  • I have written necessary rustdoc comments.
  • I have added necessary unit tests and integration tests.
  • I have added test labels as necessary.
  • I have added fuzzing tests or opened an issue to track them.
  • My PR contains breaking changes.
  • My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
  • My PR contains critical fixes that are necessary to be merged into the latest release.

Documentation

  • My PR needs documentation updates.
Release note

@BugenZhao BugenZhao marked this pull request as ready for review December 18, 2024 08:01
Copy link
Member

@yezizp2012 yezizp2012 left a comment

Choose a reason for hiding this comment

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

LGTM!

@@ -0,0 +1,4 @@
disallowed-methods = [
{ path = "sea_query::table::column::ColumnDef::binary", reason = "Please use `.rw_binary(..)` instead." },
Copy link
Member

Choose a reason for hiding this comment

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

Can you explain it by some comments?

Copy link
Member Author

@BugenZhao BugenZhao Dec 19, 2024

Choose a reason for hiding this comment

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

Yes, it's explained in docs:

/// Set column type as `longblob` for MySQL, `bytea` for Postgres, and `blob` for Sqlite.
///
/// Should be preferred over [`binary`](ColumnDef::binary) or [`blob`](ColumnDef::blob) for large binary fields,
/// typically the fields wrapping protobuf or other serialized data. Otherwise, MySQL will return an error
/// when the length exceeds 65535 bytes.

@graphite-app graphite-app bot requested a review from a team December 19, 2024 03:51
Comment on lines -13 to +19
.add_column(ColumnDef::new(Connection::Params).binary().not_null())
.add_column(
ColumnDef::new(Connection::Params)
.rw_binary(manager)
.not_null(),
)
Copy link
Member

Choose a reason for hiding this comment

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

Is it correct to directly change an existing migration script? Not sure, just want to confirm.

Copy link
Member

Choose a reason for hiding this comment

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

Only for MySQL, I think it's okay.

@BugenZhao BugenZhao added this pull request to the merge queue Dec 23, 2024
Merged via the queue into main with commit 6d4f966 Dec 23, 2024
32 of 33 checks passed
@BugenZhao BugenZhao deleted the bz/main-cron-mysql-backend branch December 23, 2024 05:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants