If I make 10 mutations continuously and add 2 nodes for each mutation, but I don’t commit them. And then I commit all of them at last. My question is : How many transactions are there for the DGraph at this point?

[image] CalicoBox: How many transactions are there for the DGraph at this point? 10 transactions, or maybe one. It depends how you did it. You can have many mutations creating many nodes using the same transaction.

When I do a mutation by rest api { set { <0x1> <balance> "110" . <0x2> <balance> "60" . } } I’ll get 2 keys. What dose the keys means? Will the number of ts such as ‘4’ not change as long as the ts remains unchanged?

[image] CalicoBox: I’ll get 2 keys. What dose the keys means? Means represent the state of that transaction. You use those to commit or discard. If you do not, it will be discarded soon. [image] CalicoBox: Will the number of ts such as ‘4’ not change as long as the ts remains unchanged? …

Thanks for your response. In fact, the reason why I ask the question is that I encountered a problem when I try to update some data by spark task. The spark task blocked after running for some time. It seemed that transactions were stacked. (After I killed the spark task, I tried to do some queries…

[image] CalicoBox: Will it work? Any suggestions please. I don’t see why not. But I never used any spark tasks myself. [image] CalicoBox: There is how I update data: You don’t need to delete, if you mutate in a filled predicate of an existing Node it will be overwritten.

For DGraph, do deletes cost more than adds? If so, the way may change to : get the uids of one node and the nodes that can get through “prdicate_1” . { test(func: eq(name, "test1")){ uid predicate_1 { uid } } } put a delete mark on all the edges of the node. { set …

About the number of transaction

Users Dgraph

CalicoBox (Calico Box) November 22, 2018, 3:40am 9

However, it is possible to have too many transactions, does the DGraph have any strategy for this situation?

The question is irrelevant to the topic, so I open a new one.

Topic		Replies	Views
Transactions in GraphQL Dev graphql , rfc , eng	27	11904	September 1, 2022
Upper Transaction Mutation Limit - Concurrent Mutation Processing? Dgraph	0	248	December 22, 2023
Transaction using GQL GraphQL kind:question	3	1207	November 17, 2020
Transactions in Dgraph Users	2	2296	October 25, 2017
Cost of each mutation grows as more mutations are in a transaction Dgraph dgraph , kind:enhancement , status:accepted , priority:p1 , area:performance	2	562	February 21, 2019

About the number of transaction

Related topics