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

ct: add ::ContinualTask to various adapter enums #29675

Merged
merged 1 commit into from
Sep 25, 2024

Conversation

danhhz
Copy link
Contributor

@danhhz danhhz commented Sep 19, 2024

May as well rip off the band-aid and get it over with.

Touches MaterializeInc/database-issues#8427

Motivation

  • This PR adds a known-desirable feature.

Tips for reviewer

This is the first time I've had to make a change to the catalog protos, and I think I missed some steps :)

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@danhhz danhhz requested a review from ParkMyCar September 19, 2024 20:24
@danhhz danhhz requested review from a team as code owners September 19, 2024 20:24
@danhhz danhhz changed the title ct: add ::ContinualTask various adapter enums ct: add ::ContinualTask to various adapter enums Sep 19, 2024
"max_continual_tasks",
value!(u32; 100),
"The maximum number of continual_tasks in the region, across all schemas (Materialize).",
true,
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 makes the existence of CTs externally visible outside of mz_internal, but that seems better than me forgetting to flip it to public later 🤷 (Also, trying hard to not accumulate more TODO(ct)s, I have plenty)

@danhhz danhhz requested a review from a team as a code owner September 20, 2024 20:58
Copy link
Member

@ParkMyCar ParkMyCar left a comment

Choose a reason for hiding this comment

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

Nice!!

Not something you need to do in this PR, but to support comments on Continual Tasks we will need to add the new variant of CommentObjectType in planning.

@@ -6750,6 +6774,31 @@ ORDER BY 1, 2"#,
access: vec![PUBLIC_SELECT],
});

pub static MZ_SHOW_CONTINUAL_TASKS: LazyLock<BuiltinView> = LazyLock::new(|| BuiltinView {
Copy link
Member

Choose a reason for hiding this comment

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

Not required in this PR but we generally index the SHOW X commands, example

@danhhz
Copy link
Contributor Author

danhhz commented Sep 24, 2024

Sounds good! Given the amount of time I have this week and how likely it is that this will rot, I might pick those two up as TODO(ct)s :). Will add those, rebase, get a nightlies in, and see if I can get this merged

May as well rip off the band-aid and get it over with.
@danhhz
Copy link
Contributor Author

danhhz commented Sep 25, 2024

TFTR!

@danhhz danhhz merged commit 01e0078 into MaterializeInc:main Sep 25, 2024
212 of 217 checks passed
@danhhz danhhz deleted the ct_todos_adapter branch September 25, 2024 14:07
danhhz added a commit to danhhz/materialize that referenced this pull request Sep 27, 2024
Followups from MaterializeInc#29675.

Plus resolve a couple other small TODOs.
@danhhz danhhz mentioned this pull request Sep 27, 2024
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants