remaining provenance issues for 2.1 release
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.
#1 Updated by Derik Barseghian almost 9 years ago
As requested I've posted a description on the wiki describing these issues: