Skip to content

Place bounded lineage metrics under a new name.#33482

Merged
robertwb merged 1 commit intoapache:masterfrom
robertwb:bounded-trie-lineage-name
Jan 13, 2025
Merged

Place bounded lineage metrics under a new name.#33482
robertwb merged 1 commit intoapache:masterfrom
robertwb:bounded-trie-lineage-name

Conversation

@robertwb
Copy link
Copy Markdown
Contributor

@robertwb robertwb commented Jan 2, 2025

This avoids any potential complexities with mixing old and new metrics with the same name but different types (e.g. after a streaming update across an sdk upgrade).


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests
Go tests

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

This avoids any potential complexities with mixing old and new
metrics with the same name but different types (e.g. after a
streaming update across an sdk upgrade).
@robertwb
Copy link
Copy Markdown
Contributor Author

robertwb commented Jan 2, 2025

R: @rohitsinha54

@github-actions github-actions bot added the python label Jan 2, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 2, 2025

Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control. If you'd like to restart, comment assign set of reviewers

@damccorm
Copy link
Copy Markdown
Contributor

@robertwb is this ready to be merged?

@robertwb
Copy link
Copy Markdown
Contributor Author

@robertwb is this ready to be merged?

Yes. Thanks for the ping.

@robertwb robertwb merged commit 4611a81 into apache:master Jan 13, 2025
LINEAGE_NAMESPACE = "lineage"
SOURCE = "sources"
SINK = "sinks"
SOURCE = "sources_v2"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Since metrics are namespaced would it be better to do keep name sources and sinks itself and change the namespace to lineage_v2?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The division between the namespace and non-namespace portion of a name are somewhat arbitrary... Keeping the namespace the same is nice because it allows one to query for all lineage counters (even as they evolve) but I don't feel too strongly about this.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

SG. I agree either way is fine. Lets keep the namespace common then. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants