Skip to content
Discussion options

You must be logged in to vote

khepri_mnesia_migration migration doesn't double-check but it subscribes to Mnesia changes. Therefore, it won't miss changes happening in parallel to the initial copy.

This exception is a bug: in some place we apparently forget to "unpack" the {Module, Arguments} tuple before calling Module:delete_from_khepri().

Replies: 2 comments 7 replies

Comment options

You must be logged in to vote
2 replies
@dumbbell
Comment options

Answer selected by michaelklishin
@michaelklishin
Comment options

Comment options

You must be logged in to vote
5 replies
@markusgust
Comment options

@mkuratczyk
Comment options

@markusgust
Comment options

@markusgust
Comment options

@the-mikedavis
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
5 participants