[kepler-dev] [Bug 5424] New: see if it's worthwhile to upgrade hsql from 1.8

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5424

           Summary: see if it's worthwhile to upgrade hsql from 1.8
           Product: Kepler
           Version: 2.1.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: provenance
        AssignedTo: crawl at sdsc.edu
        ReportedBy: barseghian at nceas.ucsb.edu
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


Currently hsql is at v2.2, but we're still using 1.8. There are a number of
benefits to upgrading to 2.2. Dan and I discussed it and it seems worthwhile to
test, esp to see if performance improves -- we have some really poor
performance in some areas. E.g. the growingDegreeDays workflow with days set to
300 can take up to 13m to run with provenance turned on, but <10s with
provenance turned off. And bug#5413 discusses how large run deletion from WRM
can take way too long.

I tried to upgrade my 1.8 provenance data to 2.2 today, but wasn't able to. I
couldn't get a connection made to the db from 2.2.  There are errors about the
first ALTER line in the provenanceDB.script file:

org.hsqldb.HsqlException: error in script file line: 49 invalid expression in
CHECK or GENERATED clause in statement [ALTER TABLE WORKFLOW_EXEC ADD
CONSTRAINT WORKFLOW_EXEC_WF_ID_FK FOREIGN KEY(WF_ID) REFERENCES WORKFLOW(ID) ON
DELETE CASCADE]

I spent some time manually hacking the script file, but wasn't able to figure
out what's wrong here...

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.