You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating the CollectionSpace::Mapper::DataHandler with the refcache created on the connection object caused a bug when you process a batch with {"check_terms": false} in the batch configuration.
I was unable to reproduce the issue within the collectionspace-mapper and therefore couldn't track it down to fix it there.
This commit changed how the DataHandler gets created for a batch, and fixed the bug.
However it relies on offloading the creation of the refcache to collectionspace-mapper, which we probably don't really want to do in production because collectionspace-mapper doesn't know about Redis, etc...
The text was updated successfully, but these errors were encountered:
Creating the
CollectionSpace::Mapper::DataHandler
with the refcache created on the connection object caused a bug when you process a batch with{"check_terms": false}
in the batch configuration.I was unable to reproduce the issue within the
collectionspace-mapper
and therefore couldn't track it down to fix it there.This commit changed how the
DataHandler
gets created for a batch, and fixed the bug.However it relies on offloading the creation of the refcache to
collectionspace-mapper
, which we probably don't really want to do in production becausecollectionspace-mapper
doesn't know about Redis, etc...The text was updated successfully, but these errors were encountered: