Enable ability to delete AI Platform training jobs [167533584]

Assigned

Feature Request

Status Update

No update yet.

Description

na...@gmail.com

created issue #1

Sep 2, 2020 04:31PM

It would be great if we could delete old AI Platform training jobs. Ideally, this could be done using the Console or by submitting a CURL/REST request. It's actually not important to me that it deletes the files created in GCS, as the main purpose would be to 1) significantly reduce the clutter on the UI, 2) make it easier to track experiments, 3) reduce the time needed to LIST jobs, which would help with other issues like

https://issuetracker.google.com/167285811.

I have a lot of "test" training jobs that are for pure experimentation purposes only. I'd like to now delete these and start from a clean slate.

Comments

pg...@google.com <pg...@google.com> #2Sep 3, 2020 07:49AM

Hello,

Thank you for reaching out.

This issue was forwarded to our product team. Please keep in mind that this issue has to be analyzed and considered by the product team and I can't provide you ETA for it to be delivered. However, you can keep track of the status by following this thread.

Kind Regards

na...@gmail.com <na...@gmail.com> #3Jan 4, 2021 09:06PM

Is there any update on this issue?

is...@gmail.com <is...@gmail.com> #4Jun 2, 2021 09:12AM

Hello,

Thank you for your patience.

Our product team is currently working on it. Once there will be an update it will be shared in this thread.

Kind Regards

na...@gmail.com <na...@gmail.com> #5Jun 3, 2021 07:36PM

Are there any alternative solutions or workarounds that would allow us to access the pipeline run id? This functionality is useful for us to be able to correlate our predictions with the pipeline runs that created them. And that in turn can help analysis/troubleshooting.

is...@gmail.com <is...@gmail.com> #6Jun 4, 2021 07:06AM

Hello,

Thank you for reaching out. Our internal team is handling the case. Unfortunately there are no updates about it. For now, please stay tune to this thread for updates.

Regards,

sh...@google.com <sh...@google.com> #7Jun 11, 2021 02:13PM

Assigned to gc...@google.com.

Hello,

Quick update about this. Our team mentions that for Vertex Pipelines, we have a different set of placeholders, the currently implemented ones are names and uuids. Here's an example of using them: https://github.com/kubeflow/pipelines/blob/master/sdk/python/kfp/v2/compiler_cli_tests/test_data/pipeline_with_placeholders.py

Let me know if this helps you with your case.

Regards,

is...@gmail.com <is...@gmail.com> #8Jun 17, 2021 02:52PM

Hello

Quick update, this has been delayed. Please stay tune for further for updates.

Regards

mu...@google.com <mu...@google.com> #9Jun 20, 2021 06:49PM

As a workaround, you can specify a run ID when you invoke the pipeline and then additionally pass that run ID as an input parameter to your pipeline so that you can access it.

is...@gmail.com <is...@gmail.com> #10Apr 5, 2022 01:53PM

Hello

Thank you for providing the workaround, I will forward that to the google team. Please stay tune to this thread for updates.

Regards,

sh...@tv4.se <sh...@tv4.se> #11Apr 26, 2023 09:06AM

Since AI Platform is being phased out (for Vertex AI which I don't think is production-ready yet here it is), I wouldn't assume there would be any new updates on this. It's April 2023 now. I believe these jobs are still undeletable.

Issue 167533584

Description

Issue summary

Comments

pg...@google.com <pg...@google.com> #2Sep 3, 2020 07:49AM

na...@gmail.com <na...@gmail.com> #3Jan 4, 2021 09:06PM

is...@gmail.com <is...@gmail.com> #4Jun 2, 2021 09:12AM

na...@gmail.com <na...@gmail.com> #5Jun 3, 2021 07:36PM

is...@gmail.com <is...@gmail.com> #6Jun 4, 2021 07:06AM

sh...@google.com <sh...@google.com> #7Jun 11, 2021 02:13PM

is...@gmail.com <is...@gmail.com> #8Jun 17, 2021 02:52PM

mu...@google.com <mu...@google.com> #9Jun 20, 2021 06:49PM

is...@gmail.com <is...@gmail.com> #10Apr 5, 2022 01:53PM

sh...@tv4.se <sh...@tv4.se> #11Apr 26, 2023 09:06AM

Add comment

Issue metadata