Mutation variables go away since v0.9.0

selmeci · January 24, 2018, 6:16pm

Hi everyone,

according to github, mutation variables are no longer supported since version 0.9.0.

According to release note, this functionality can now easily be achieved via transactions.
Unfortunatly, I cannot find any example how to do it.

Does anyone any example?

Thank you.

sboorlagadda · January 24, 2018, 6:45pm

Hello Selmeci,

Transaction do provide a way to do query and use the queried results to mutate with in your transaction.
Let me know if this example helps

github.com

dgraph-io/dgraph4j/blob/master/src/test/java/io/dgraph/AcctUpsertTest.java#L55


      for (int age : ages) {
        Account account = new Account();
        account.first = first;
        account.last = last;
        account.age = age;
        accounts.add(account);
      }
    }
  }

  String schema =
      ""
          + "   first:  string   @index(term) @upsert .\n"
          + "   last:   string   @index(hash) @upsert .\n"
          + "   age:    int      @index(int)  @upsert .\n"
          + "   when:   int                   .\n";
  Operation op = Operation.newBuilder().setSchema(schema).build();
  dgraphClient.alter(op);
}

private void tryUpsert(Account account) {

Sai

system · February 23, 2018, 6:45pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Javascript client: Are variables supported in mutation blocks? Users	6	661	February 27, 2018
Major changes in v0.9 Announce	56	4793	December 13, 2017
How to set variable in mutation during upsert? Dgraph kind:question , area:upsert	5	919	November 2, 2020
Query Then Mutate in Ratel Users	6	883	April 21, 2018
Struggled at making upsert with assignment via the dgo client Dgraph	5	361	March 15, 2020

Mutation variables go away since v0.9.0

Related topics