Steps to reproduce:
1. Create offline capture (e.g. with TheRec)
2. Upload with option "Trim"
3. Capture gets processed correct until hold to trim
4. Trim and confirm
5. The further encoding ends with
Actual Results: see above
Expected Results: final completion of the workflow
Workaround (if any): not known
Karen, that commit removes the constraint in the Java annotation, but does leave the mysql5.sql file untouched, so the table job_argument still has that constraint in place. Are you suggesting that should be removed from the database defintion too?
This issue has been fixed by https://opencast.jira.com/browse/MH-9828
Entwine - Knowledge In Motion
You received this message because you are subscribed to the Google Groups "Matterhorn" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/a/opencast.org/group/matterhorn/.
Changing the status to fixed, no review needed with reference to MH-9828. Just in case this issue comes back, so people know it was an issue that was resolved by another ticket.
Changing closed status to better related this ticket to the other tickets involved in the mh_job_argument table unique constraint issue.