Project

General

Profile

Actions
Copy link

Bug #5410

closed

provenance data is not flushed to HSQL database before Kepler quit.

Added by jianwu jianwu over 13 years ago. Updated over 13 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Daniel Crawl
Category:
provenance
Target version:
reporting-2.3.0
Start date:
05/24/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5410

Description

Currently, provenance data writing to HSQL database has write delay (100 ms by default). It causes some data is not update or written because the data is not flushed before Kepler quit.

To reproduce it,

1) Run workflow in Kepler GUI or non-GUI mode.
2) Quit Kepler if Kepler is run in GUI mode right after workflow is executed.
3) Use HSQL client to connect hsql provenance database.
4) Check 'workflow_exec' table: the record the execution might not be written in the database or the execution status might be always 'running'.

It should work for both GUI mode or non-GUI mode. Not sure whether it works for other databases, such as Oracle and mySQL.

Actions
Copy link

Also available in: Atom PDF