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(frontend): support create iceberg source #14971

Merged
merged 18 commits into from
Feb 23, 2024

fmt

5556ad2
Select commit
Loading
Failed to load commit list.
Merged

feat(frontend): support create iceberg source #14971

fmt
5556ad2
Select commit
Loading
Failed to load commit list.
Task list completed / task-list-completed Started 2024-02-21 14:58:46 ago

0 / 8 tasks completed

8 tasks still to be completed

Details

Required Tasks

Task Status
Related issue #14742 Incomplete
Support create iceberg source. Incomplete
iceberg source could not be used in streaming queries. Incomplete
iceberg source enumerator only checks source schema against iceberg schema. Incomplete
Because iceberg source has its own row format and doesn't need to be specified by users explicitly, we could omit it. Incomplete
I have written necessary rustdoc comments Incomplete
I have added necessary unit tests and integration tests Incomplete
I have added test labels as necessary. See details. Incomplete
I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934). Incomplete
My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future). Incomplete
All checks passed in ./risedev check (or alias, ./risedev c) Incomplete
My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details) Incomplete
My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users) Incomplete
Understand the implications of revoking this secret by investigating where it is used in your code. Incomplete
Replace and store your secret safely. Learn here the best practices. Incomplete
Revoke and rotate this secret. Incomplete
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. Incomplete
following these best practices for managing and storing secrets including API keys and other credentials Incomplete
install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation. Incomplete