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

give mz_analytics select access to a few more builtin views #29796

Merged
merged 1 commit into from
Oct 1, 2024

Conversation

doy-materialize
Copy link
Contributor

Motivation

we want to be able to run internal analytics queries on mz_recent_activity_log_redacted

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.

@@ -3075,7 +3081,7 @@ pub static MZ_STATEMENT_LIFECYCLE_HISTORY: LazyLock<BuiltinSource> =
// TODO[btv]: Maybe this should be public instead of
// `MONITOR_REDACTED`, but since that would be a backwards-compatible
// chagne, we probably don't need to worry about it now.
access: vec![SUPPORT_SELECT, MONITOR_REDACTED_SELECT, MONITOR_SELECT],
Copy link
Member

Choose a reason for hiding this comment

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

I'm worried this will drop/recreate the source, and blow away all the data. Worth either double checking locally that this does not happen, or (probably easier) just omitting this one for now.

Copy link
Member

Choose a reason for hiding this comment

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

(The views are fine because dropping/recreating a view doesn't touch any data on S3.)

Copy link
Member

Choose a reason for hiding this comment

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

Never mind. @jkosh44 confirmed on Slack that this won't cause the source to be recreated.

https://materializeinc.slack.com/archives/C07ETTHQKSM/p1727732449014049?thread_ts=1727728753.597539&cid=C07ETTHQKSM

@doy-materialize doy-materialize merged commit fdc89ef into main Oct 1, 2024
74 checks passed
@doy-materialize doy-materialize deleted the doy-analytics-views branch October 1, 2024 01:38
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