Interesting.  It sounds to me like there are two problems here, with a
common source:

o  a (potentially) gigantic transaction is built up over a sequence of
   operations which should be unrelated;

o  a (potentially) gigantic queue of events which should be unrelated
   is built up within the curation run's Context.

It sounds to me as though none of the tasks in the run is committing
its work.  The default curation scope is OPEN, so Curator is not
committing.  The event handler in question commits its own work, and
in so doing, the first time it is called by the dispatcher,
inadvertently commits all of the *other* curation work that should
have been committed already.

I can find no documentation for this, but it appears that event
handlers should not commit work.  The design of Context seems to
depend on this.  If true, we should document this requirement
thoroughly.

++++++++++++++++++

It seems to me that a task designed to be run in OPEN scope must
commit its own work.  There is, however, a problem with this:  Context
contains only one Session.  A bulk operation needs to keep a
transaction open while it consumes the sequence of entities on which
it is to operate, and also to be able to commit work (closing a
transaction) whenever it modifies one of those entities.  I suppose
that one could work around this by draining the sequence into a List
and then reloading them one at a time for processing, but how
inefficient that is!

-- 
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/ZBshlJKj9oObgZOi%40IUPUI.Edu.

Attachment: signature.asc
Description: PGP signature

Reply via email to