feat: specify column when sink into table #16587
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
st1page
commented
May 6, 2024
Comment on lines
+48
to
52
| /// If columns is empty, it means that the user did not specify the column names. | ||
| /// In this case, we extract the column names from the query. | ||
| /// If columns is not empty, it means that user specify the column names and the user | ||
| /// should guarantee that the column names number are consistent with the query. | ||
| pub(super) fn get_column_names( |
There was a problem hiding this comment.
will do some refactor for the function later. I guess some check should be done in other place instead of here, this PR focus on the feature and not contain it.
4 tasks
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 9425213 | Triggered | Generic Password | f5b9c1b | e2e_test/source/cdc/cdc.validate.postgres.slt | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 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.
Co-authored-by: Eric Fu <[email protected]>
…risingwavelabs/risingwave into sts/specify_column_when_sink_into_table
st1page
added a commit
that referenced
this pull request
May 11, 2024
Co-authored-by: Eric Fu <[email protected]>
github-merge-queue bot
pushed a commit
that referenced
this pull request
May 12, 2024
Co-authored-by: Eric Fu <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
implement https://github.com/risingwavelabs/risingwave-docs/pull/1860/files#diff-1aea3471e5edab47e46b22768bb6edf6b5fcbb17efe99a91fcbd28df79a15a94
a part of #15515
Checklist
./risedev check(or alias,./risedev c)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.