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

[dagster-fivetran] tests tweak to avoid duplicate asset keys #19920

Merged
merged 1 commit into from
Feb 20, 2024

Conversation

smackesey
Copy link
Collaborator

@smackesey smackesey commented Feb 20, 2024

Summary & Motivation

See https://github.com/dagster-io/dagster/pull/19879/files#r1493423916 for context.

Some dagster-fivetran tests create duplicate asset keys when using multiple connectors. This changes the tests to use unique asset keys.

How I Tested These Changes

The tests still pass (and also pass upstack where they started failing).

Base automatically changed from sean/sensor-tweak to master February 20, 2024 20:42
@smackesey smackesey force-pushed the sean/fivetran-tests-tweak branch from 1d6e2ce to ae91a5a Compare February 20, 2024 20:44
@smackesey smackesey merged commit 7bfb40b into master Feb 20, 2024
1 check was pending
@smackesey smackesey deleted the sean/fivetran-tests-tweak branch February 20, 2024 20:45
PedramNavid pushed a commit that referenced this pull request Mar 28, 2024
## Summary & Motivation

See https://github.com/dagster-io/dagster/pull/19879/files#r1493423916
for context.

Some `dagster-fivetran` tests create duplicate asset keys when using
multiple connectors. This changes the tests to use unique asset keys.

## How I Tested These Changes

The tests still pass (and also pass upstack where they started failing).
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