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

feat(copy dataset): Allow API to determine if target dataset exists #3289

Conversation

vquigley
Copy link
Contributor

@vquigley vquigley commented May 13, 2022

Description

Allow API to determine if the target dataset exists or if a copy job is currently in progress.
New functionality in API to determine the difference between existing dataset and running job.
Stops confusion when a copy job is in progress but the UI says "dataset name already exists".

What to review

Simply removing a check against local storage.

Notes for release

New functionality in API to determine the difference between existing dataset and running job.
CLI will now let the API determine the state of the target dataset.

@vquigley vquigley requested review from rexxars and dcilke May 13, 2022 14:57
@vercel
Copy link

vercel bot commented May 13, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
perf-studio ✅ Ready (Inspect) Visit Preview May 13, 2022 at 3:15PM (UTC)
studio-workshop ✅ Ready (Inspect) Visit Preview May 13, 2022 at 3:15PM (UTC)
test-studio ✅ Ready (Inspect) Visit Preview May 13, 2022 at 3:15PM (UTC)

Comment on lines -145 to -147
if (existingDatasets.includes(targetDatasetName)) {
throw new Error(`Target dataset "${targetDatasetName}" already exists`)
}
Copy link
Member

Choose a reason for hiding this comment

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

Do we need to make any changes to the error logging?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No, it gets caught in the same set of statements we already use.

Copy link
Contributor

@RitaDias RitaDias left a comment

Choose a reason for hiding this comment

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

✅ This looks good!

@vquigley vquigley merged commit 0b4f022 into next May 30, 2022
@vquigley vquigley deleted the feature/sc-18216/better-error-when-a-duplicate-job-is-in-progress branch May 30, 2022 10:54
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.

4 participants