Bug 2215093 - Optimize DockerMetaTag query and CV version deletion to run a single invocation of the method.
Summary: Optimize DockerMetaTag query and CV version deletion to run a single invocati...
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.14.0
Assignee: Samir Jha
QA Contact: David Moore
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-14 17:48 UTC by Samir Jha
Modified: 2023-08-16 19:38 UTC (History)
3 users (show)

Fixed In Version: rubygem-katello-4.9.0.7-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 36500 0 Normal Ready For Testing Optimize DockerMetaTag query and CV version deletion to run a single invocation of the method. 2023-06-15 14:12:32 UTC
Red Hat Issue Tracker SAT-18262 0 None None None 2023-06-14 20:49:27 UTC
Red Hat Issue Tracker SAT-18418 0 None None None 2023-06-14 20:50:39 UTC

Description Samir Jha 2023-06-14 17:48:26 UTC
Test performance improvement between current query:

self.where("id not in (?) OR (schema2_id IS NULL AND schema1_id IS NULL)", Katello::RepositoryDockerMetaTag.pluck(:docker_meta_tag_id) + [0]).delete_all

vs 

self.where("(id != 0 and id not in (select docker_meta_tag_id from #{Katello::RepositoryDockerMetaTag.table_name})) OR (schema2_id IS NULL AND schema1_id IS NULL) ").delete_all

Also, have this method called once per CV version delete vs once per CV version repo delete to save unnecessary calls.

Comment 1 Samir Jha 2023-06-14 17:48:31 UTC
Created from redmine issue https://projects.theforeman.org/issues/36500

Comment 2 Samir Jha 2023-06-14 17:48:32 UTC
Upstream bug assigned to None

Comment 4 Bryan Kearney 2023-07-21 00:03:17 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36500 has been resolved.


Note You need to log in before you can comment on or make changes to this bug.