search

janelia-flyem / dvid

Distributed, Versioned, Image-oriented Dataservice
http://dvid.io
Other
195 stars 33 forks source link

After cleave, the new body should have a non-zero mutation ID #354

Closed stuarteberg closed 1 year ago

stuarteberg commented 3 years ago

Here's a recent cleave event from our VNC server:

{
  "Action": "cleave",
  "App": "Neu3",
  "CleavedLabel": 162018,
  "CleavedSupervoxels": [23972152129, 23972152291, 24378962479, 24378962480, 24382457474, 24382457654, 24382497952, 24382499918, 24382500352, 24382500782, 24382500828, 24382502066, 24382502502, 24382502590, 24382502921, 24792849709, 24792850804, 24792851915, 24792852623, 24792853004, 24792853243, 24792853429, 24792853878],
  "MutationID": 1000001700,
  "OrigLabel": 69896,
  "Timestamp": "2021-03-16 21:24:37.454557758 +0000 UTC m=+780305.871619215",
  "UUID": "05280fe90579437495affcdf5afe8065",
  "User": "ribeiroc"
}

It resulted in a new body (162018). Shouldn't the new body's mutation ID match the MutationID shown in the above message? Currently, new bodies have mutation ID of 0, which seems strange to me.

$ curl http://emdata5.janelia.org:8400/api/node/05280f/segmentation/lastmod/162018
{"mutation id": 0, "last mod user": "", "last mod app": "", "last mod time": "" }
DocSavage commented 1 year ago

@stuarteberg It appears that the cleaved body label index was not properly setting the mutation ID and lastmod field, unlike the remaining label index. This has been corrected.