current implementation using retry logic and if any partial failure happen during mutations, then increment on degreeVal could be issued multiple time only because of retry logic.
This yield to inconsistent degree value when same edge is updated and deleted multiple times and when delete all outgoing/incomming edges by deleteAll.
Need way to avoid multiple increment for degree value.
current implementation using retry logic and if any partial failure happen during mutations, then increment on degreeVal could be issued multiple time only because of retry logic.
This yield to inconsistent degree value when same edge is updated and deleted multiple times and when delete all outgoing/incomming edges by deleteAll.
Need way to avoid multiple increment for degree value.