dGraph 20.03 beta, importing dump from 1.2.2 fails

Users Dgraph
1

Hello,
I just tried last dGraph version, but I cannot import my RDF backup made with a 1.2.2, I get this error:

Dgraph version   : v20.03.0-beta.20200320
Dgraph SHA-256   : c92511f46c386fb173339cd25ce38fa3fb6b79c9daa83d8768f92acbb1771d0e
Commit SHA-1     : cc10d2ad
Commit timestamp : 2020-03-20 16:18:05 -0700
Branch           : HEAD
Go version       : go1.14.1

For Dgraph official documentation, visit https://docs.dgraph.io.
For discussions about Dgraph     , visit http://discuss.dgraph.io.
To say hi to the community       , visit https://dgraph.slack.com.

Licensed variously under the Apache Public License 2.0 and Dgraph Community License.
Copyright 2015-2020 Dgraph Labs, Inc.


panic: interface conversion: interface {} is nil, not int64

goroutine 171 [running]:
github.com/dgraph-io/dgraph/tok.IntTokenizer.Tokens(...)
	/tmp/go/src/github.com/dgraph-io/dgraph/tok/tok.go:193
github.com/dgraph-io/dgraph/tok.BuildTokens(0x0, 0x0, 0x1b5c980, 0x26061d0, 0x1b5c980, 0x26061d0, 0x0, 0x1, 0xc0013a3bc0)
	/tmp/go/src/github.com/dgraph-io/dgraph/tok/tok.go:107 +0x63
github.com/dgraph-io/dgraph/dgraph/cmd/live.(*loader).conflictKeysForNQuad(0xc0005461c0, 0xc000da9950, 0x8, 0x1, 0x1, 0x0, 0x0)
	/tmp/go/src/github.com/dgraph-io/dgraph/dgraph/cmd/live/batch.go:313 +0x497
github.com/dgraph-io/dgraph/dgraph/cmd/live.(*loader).conflictKeysForReq(0xc0005461c0, 0xc00194bf78, 0xc0011c6001, 0x7d0, 0x800)
	/tmp/go/src/github.com/dgraph-io/dgraph/dgraph/cmd/live/batch.go:334 +0xe6
github.com/dgraph-io/dgraph/dgraph/cmd/live.(*loader).makeRequests(0xc0005461c0)
	/tmp/go/src/github.com/dgraph-io/dgraph/dgraph/cmd/live/batch.go:396 +0x1af
created by github.com/dgraph-io/dgraph/dgraph/cmd/live.setup
	/tmp/go/src/github.com/dgraph-io/dgraph/dgraph/cmd/live/run.go:361 +0x2f0
, exit status 2
2

Hey, can you give a small sample that I could reproduce it?

PS. This was confirmed by the user dataset and schema. We are analyzing it internally the fix for next beta release.

3

@MichelDiz told me it’s a known and fixed bug, but not on this branch yet. An alternative is using bulk import, until next version.

4

I have the same issue with this client loading a bulk set (separate json files) using live, and then reloading it again using the same cli command pointing to the xidmap created by the initial run. Running server 1.2.2 (21cc8936)

5

The fix is on master and it will be cherry picked for all latest versions (v20.x.x and v1.x.x).