Project

General

Profile

Bug #5158

remaining provenance issues for 2.1 release

Added by Derik Barseghian about 9 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
provenance
Target version:
Start date:
08/20/2010
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5158

Description

There are some remaining tasks to be done for provenance before we can ship 2.1:
- Dan has some schema changes to put in
- We need to start keeping more detailed versioning information about provenance in the schema (right now the version column contains the major version of the provenance schema, e.g. 8)
- We need an upgrade process in place to upgrade an old store.
- The HSQLDB provenance stores are now in version'd dirs, we also need to write the provenance configuration files into these dirs, so a user can config one version of kepler to connect to a custom store, and not have this trampled by a subsequent version of kepler.

Our current plan is to upgrade provenance stores as necessary with new versions of provenance, but the new store is created from the old, and the old is left in tact. It will be up to the user if they want to keep their old prov store around, they will need it if they ever want to open an older run when in Strict mode, unless they have already exported this run into a kar.

History

#1 Updated by Derik Barseghian almost 9 years ago

As requested I've posted a description on the wiki describing these issues:
https://kepler-project.org/developers/interest-groups/provenance-interest-group/provenance-and-versioning

#2 Updated by Derik Barseghian almost 9 years ago

Retargeting, Dan did what needed doing for 2.1.

#3 Updated by Daniel Crawl about 8 years ago

Upgrade process done.

#4 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5158

Also available in: Atom PDF