Ticket #447 (closed new functionality: fixed)

Opened 11 years ago

Last modified 7 years ago

Support database for multiple DC3 runs (R&D needed)

Reported by: jbecla Owned by: jbecla
Priority: normal Milestone:
Component: database Keywords:
Cc: smm Blocked By:
Blocking: #460 Project: LSST
Version Number:
How to repeat:

not applicable

Description

In DC2 each test run had a separate copy of the database catalogs. In DC3, this is impractical, we need to come up with a scheme that allows multiple runs to share database. Related document: dbPipelineDbSetup.

Change History

comment:1 Changed 11 years ago by jbecla

  • Status changed from new to assigned
  • Blocked By 426 added

comment:2 Changed 11 years ago by jbecla

  • Milestone set to DC3a MW DB

comment:3 Changed 11 years ago by jbecla

  • Blocked By 460 added

comment:4 Changed 11 years ago by jbecla

  • Blocking 460 added
  • Blocked By 460 removed

comment:5 Changed 11 years ago by jbecla

  • Owner changed from jbecla to Tim Axelrod
  • Status changed from assigned to needinfo

Tim: we would like to better understand how the output from DC3 will be queried by users debugging DC3. Please see dbPipelineDbSetup, in particular "Approach without views and without merge table" section. Would it be sufficient to implement this?

comment:6 Changed 11 years ago by jbecla

  • Owner changed from TimAxelrod to jbecla
  • Status changed from needinfo to assigned

comment:7 Changed 11 years ago by jbecla

  • Blocked By 426 removed

comment:8 Changed 11 years ago by jbecla

  • Cc smm added
  • Status changed from assigned to closed
  • Resolution set to fixed

Per discussion at the DataAccWG telecon 12/2/08, this is not needed:

  • in DC3a the Object Catalog will be relatively small
  • in DC3b we will always start with an empty Object Catalog.

The only remaining task is automated run deletion, this is now covered in ticket #511

comment:9 Changed 7 years ago by robyn

  • Milestone DC3a MW DB deleted

Milestone DC3a MW DB deleted

Note: See TracTickets for help on using tickets.