Dgraph v1.1.0-rc2 release candidate


(Daniel Mai) #1

Hey folks,

Please try out our latest release candidate v1.1.0-rc2. If you find any issues, please let us know so we can address them before the final v1.1.0.

The full list of changes for v1.1.0 is available in the CHANGELOG. There are LOTS of significant changes and features in this version. They’re all covered in the CHANGELOG, so please take a look and let us know what you think! Dgraph v1.1 is NOT backwards compatible with Dgraph v1.0.

Link to binaries: Linux, Darwin, Windows.

Also published on Docker tagged as v1.1.0-rc2.

Note: This is not the official release. You won’t be able to get these binaries using the get.dgraph.io quick install script.

$ dgraph version

Dgraph version   : v1.1.0-rc2
Dgraph SHA-256   : 1349c2c2e45488073fae5aa39e22ab2d91a74f1f86e85383195ae07d0dca793c
Commit SHA-1     : 9af081d1
Commit timestamp : 2019-08-23 15:41:39 -0700
Branch           : HEAD
Go version       : go1.12.7

Cheers,

The Dgraph Team


(Dody Gunawinata) #2

This issue is still not fixed https://github.com/dgraph-io/dgraph/issues/3800


(PPP225) #3

When using dgo or ratel:

assigned.Uids["blank-0"] doesn’t exist, when doing mutation without uid. Dgraph returns uids:<key:"dg.1837703885.759" value:"0x2987" >

When uid is specified during mutation, for example as _:new, then it works as expected, and can be accessed as assigned.Uids["new"].


(Daniel Mai) #4

@ppp225 dg.1837703885.759 the new format for blank nodes for JSON mutations that don’t explicitly set the "uid" JSON field.


(PPP225) #5

I see. I wondered if this was an intended change, as we can see it still being used in dgo tests

Thanks.


(Daniel Mai) #6

This was an intended change introduced in this PR:

Thanks for catching that test case in dgo. We updated the rest of them to have explicit uids, and it looks like we missed that one.