Ticket #1304 (new defect)

Opened 14 years ago

Last modified 8 years ago

Delay costly operations (rebuilds) at setup time

Reported by: fguillaume Owned by: gracinet
Priority: P2 Milestone: CPS 3.6.1
Component: CPSCore Version: TRUNK
Severity: major Keywords:


When you import a new setup for the trees tool, or for the catalog, in some cases you would have to ask for a rebuild or a reindex.

But we don't want to do these operations systematically, because they may be costly.

Instead they should be added to a persistent list (probably in portal_setup) of pending things to do by the administrator, and the administrator can run them when he wishes, in one go.

Change History

comment:1 Changed 10 years ago by gracinet

  • Owner changed from fguillaume to gracinet
  • Component changed from CPS (global) to CPSCore
  • Severity changed from normal to major

Moreover, if you import several profiles in one shot, starting from a base profile that clears the conf, you may have between profiles an inconsistent configuration, resulting in errors and broken catalogs or tree caches.

I'm tired of this -- will fix soon

comment:2 Changed 10 years ago by gracinet

  • Milestone changed from CPS 3.5.0 to CPS 3.5.1

comment:3 Changed 9 years ago by gracinet

  • Milestone changed from CPS 3.5.1 to CPS 3.5.2

After the catalog reindexing has been disabled, this can wait for 3.5.2 It's common practice to use the replaymetaprofiles.py followed by resync.py cpsjobs (defined in CPSDefault)

comment:4 Changed 8 years ago by gracinet

A current version of this noted in #2427 : the steps import could indeed save a list of resync actions to be done after all imports and the resync and replaymetaprofiles jobs could offer a facility for that.

comment:5 Changed 8 years ago by gracinet

  • Milestone changed from CPS 3.5.3 to CPS 3.5.4

Too big for 3.5.3

comment:6 Changed 8 years ago by gracinet

  • Priority changed from P1 to P2
  • Milestone changed from CPS 3.5.4 to CPS 3.6

Now that we can exclude some steps in meta profiles, this can wait a bit longer. Since that's a lot of refactoring, mostly inside the CMF export/import of catalog, this better be done in a fresher Zope/CMF context (maybe they had the use case, too)

Note: See TracTickets for help on using tickets.