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

[MAINTENANCE] Remove the need for DataContext registry in the instrumentation of the Legacy Profiler profiling method. #3836

Conversation

alexsherstinsky
Copy link
Contributor

@alexsherstinsky alexsherstinsky commented Dec 10, 2021

Scope

  • All active expectation dispatcher objects (Dataset, Batch, and Validator) have access to a DataContext instance. Hence, the usage of the auxiliary BaseDataContext.get_data_context() registry method is not needed.
  • Update all code using the send_usage_message() utility.

Please annotate your PR title to describe what the PR does, then give a brief bulleted description of your PR below. PR titles should begin with [BUGFIX], [FEATURE], [DOCS], or [MAINTENANCE]. If a new feature introduces breaking changes for the Great Expectations API or configuration files, please also add [BREAKING]. You can read about the tags in our contributor checklist.

Changes proposed in this pull request:

  • JIRA: ANT-20/ANT-24/ANT-93

After submitting your PR, CI checks will run and @ge-cla-bot will check for your CLA signature.

For a PR with nontrivial changes, we review with both design-centric and code-centric lenses.

In a design review, we aim to ensure that the PR is consistent with our relationship to the open source community, with our software architecture and abstractions, and with our users' needs and expectations. That review often starts well before a PR, for example in github issues or slack, so please link to relevant conversations in notes below to help reviewers understand and approve your PR more quickly (e.g. closes #123).

Previous Design Review notes:

Definition of Done

Please delete options that are not relevant.

  • My code follows the Great Expectations style guide
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added unit tests where applicable and made sure that new and existing tests are passing.
  • I have run any local integration tests and made sure that nothing is broken.

Thank you for submitting!

@netlify
Copy link

netlify bot commented Dec 10, 2021

✔️ Deploy Preview for niobium-lead-7998 ready!

🔨 Explore the source changes: ad6e607

🔍 Inspect the deploy log: https://app.netlify.com/sites/niobium-lead-7998/deploys/61b3bc9e8c42c1000779a8bc

😎 Browse the preview: https://deploy-preview-3836--niobium-lead-7998.netlify.app

@github-actions
Copy link
Contributor

HOWDY! This is your friendly 🤖 CHANGELOG bot 🤖

Please don't forget to add a clear and succinct description of your change under the Develop header in docs_rtd/changelog.rst, if applicable. This will help us with the release process. See the Contribution checklist in the Great Expectations documentation for the type of labels to use!

Thank you!

Copy link
Member

@anthonyburdi anthonyburdi left a comment

Choose a reason for hiding this comment

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

LGTM!

@alexsherstinsky alexsherstinsky merged commit 7daae56 into develop Dec 10, 2021
@alexsherstinsky alexsherstinsky deleted the maintenance/ANT-20/ANT-24/ANT-93/alexsherstinsky/instrument_legacy_profiler_without_data_context_registry-2021_12_10-24 branch December 10, 2021 21:27
Shinnnyshinshin pushed a commit that referenced this pull request Dec 11, 2021
…te-with-singleton

* develop:
  [MAINTENANCE] Remove DataContext registry (#3838)
  Remove the need for DataContext registry in the instrumentation of the Legacy Profiler profiling method. (#3836)
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.

None yet

2 participants