Re: [Bug?] Updating and then removing the property in the same transaction leaves the property with an older value
Oleksandr Porunov <alexand...@...>
toggle quoted messageShow quoted text
I think this is a bug. You may raise an issue on GitHub about that.
Basically, when we updated a property and then removing this property in the same transaction, JanusGraph thinks that the property is new and remove it only from added relations inside the current transaction (i.e. remove the updated version of the property without marking it for deletion during the transaction closure). I think, we should mark the property as a modified property to resolve the issue.
As a temporary workaround, you may call "remove" 2 times for modified properties. In such case, the property will be marked for deletion and will be removed during the commit operation.
I.e. call next 4 operations to remove 2 properties:
After the issue is fixed, you will need only 1 "remove" call per each modified property. Please open the issue on GitHub about that.
On Tuesday, February 18, 2020 at 3:41:54 PM UTC-8, Bharat Dighe wrote: