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

refactor: clarify the meaning of table in TableCatalog and TableFragments #19510

Conversation

xxchan
Copy link
Member

@xxchan xxchan commented Nov 21, 2024

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

What's changed and what's your intention?

What does "table" mean is quite confusing

  • Added some comments in proto to clarify. Didn't modify proto in case of incompatibility.
  • Renamed some type and field that only exist in memory.

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

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.

Copy link
Member Author

xxchan commented Nov 21, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Base automatically changed from 11-21-refactor_rename_dummy_table_id_to_tmp_table_id to main November 21, 2024 09:02
@@ -1827,8 +1821,8 @@ impl DdlController {
// 3. Build the table fragments structure that will be persisted in the stream manager, and
// the context that contains all information needed for building the actors on the compute
// nodes.
let table_fragments = TableFragments::new(
(dummy_table_id as u32).into(),
let table_fragments = StreamJobFragments::new(
Copy link
Member

Choose a reason for hiding this comment

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

Class names are renamed while variables (or fields) still remain untouched. 😕

Copy link
Member Author

Choose a reason for hiding this comment

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

I think renaming type is more important than renaming variables. It's so hard to change all occurances. 🥺

@xxchan xxchan force-pushed the 11-21-refactor_clarify_the_meaning_of_table_in_tablecatalog_and_tablefragments branch from c78ebdd to b1c0736 Compare November 21, 2024 10:32
Signed-off-by: xxchan <[email protected]>
@xxchan xxchan requested a review from BugenZhao November 22, 2024 05:16
@xxchan xxchan enabled auto-merge November 22, 2024 05:17
Signed-off-by: xxchan <[email protected]>
Signed-off-by: xxchan <[email protected]>
@xxchan xxchan added this pull request to the merge queue Nov 22, 2024
Merged via the queue into main with commit 09a8ff3 Nov 22, 2024
34 of 35 checks passed
@xxchan xxchan deleted the 11-21-refactor_clarify_the_meaning_of_table_in_tablecatalog_and_tablefragments branch November 22, 2024 06:44
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