Project

General

Profile

Bug #14427

Content views without filters should not run index and purge steps

Added by Eric Helms over 3 years ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Performance
Target version:
Difficulty:
easy
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

An optimization with publish we can make is to check if a content view has any filters, if there are no filters then we don't need to perform certain steps such as purging errata or purging package groups. This in turn means we don't need to do the indexing associated with those actions.

History

#1 Updated by Eric Helms over 3 years ago

  • Legacy Backlogs Release (now unused) changed from 86 to 144

#2 Updated by Chris Duryee over 3 years ago

  • Bugzilla link set to 1330737

#3 Updated by Eric Helms about 3 years ago

  • Legacy Backlogs Release (now unused) changed from 144 to 168

#4 Updated by Eric Helms about 3 years ago

  • Legacy Backlogs Release (now unused) deleted (168)

#5 Updated by Justin Sherrill about 3 years ago

  • Legacy Backlogs Release (now unused) set to 114
  • Difficulty set to easy

Also available in: Atom PDF