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: skip rw's generated column when validating source #16522

Merged
merged 6 commits into from
Apr 28, 2024

Conversation

st1page
Copy link
Contributor

@st1page st1page commented Apr 28, 2024

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

The generated column is produced in risingwave rather than accessed from the external connector. So during the validation, the columns should be ignore.

Checklist

  • I have written necessary rustdoc comments
  • I have added necessary unit tests and integration tests
  • I have added test labels as necessary. See details.
  • I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
  • My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
  • All checks passed in ./risedev check (or alias, ./risedev c)
  • My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)
  • My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

  • My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

support generated column for non-shared CDC table.

@@ -181,16 +197,4 @@ impl<T: CdcSourceTypeTrait> CdcProperties<T> {
pub fn get_source_type_pb(&self) -> SourceType {
SourceType::from(T::source_type())
}

pub fn schema(&self) -> Schema {
Copy link
Contributor Author

Choose a reason for hiding this comment

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

this function is not used.

Copy link
Contributor

@tabVersion tabVersion left a comment

Choose a reason for hiding this comment

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

LGTM on the connector side.

Copy link

gitguardian bot commented Apr 28, 2024

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
9425213 Triggered Generic Password 7ac0aa0 e2e_test/source/cdc/cdc.validate.postgres.slt View secret
9425213 Triggered Generic Password 1f9eb51 e2e_test/source/cdc/cdc.validate.postgres.slt View secret
9425213 Triggered Generic Password 1f9eb51 e2e_test/source/cdc/cdc.validate.postgres.slt View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

Copy link
Contributor

@StrikeW StrikeW left a comment

Choose a reason for hiding this comment

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

LGTM

@st1page st1page enabled auto-merge April 28, 2024 09:10
@st1page st1page added this pull request to the merge queue Apr 28, 2024
Merged via the queue into main with commit 6b5b873 Apr 28, 2024
26 of 28 checks passed
@st1page st1page deleted the sts/not_valid_generated_column_on_source branch April 28, 2024 10:29
@st1page st1page added the user-facing-changes Contains changes that are visible to users label Apr 29, 2024
@xiangjinwu xiangjinwu changed the title feat: do not valid rw's generated column on source feat: skip rw's generated column when validating source May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature user-facing-changes Contains changes that are visible to users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants