Sorting on datetime field with @ cascade, creates panic

Issues GraphQL
, ,
1

Report a Dgraph Bug

What version of Dgraph are you using?

Dgraph Version

v21.03.0

Have you tried reproducing the issue with the latest release?

Its the latest version

What is the hardware spec (RAM, OS)?

Running docker container with tag v21.03-slash

Steps to reproduce the issue (command/config used to run Dgraph).

Note: added space after @ as it was giving error can’t add more than two users

type Segment {
    id: ID!
    code: String! @ id
    description: String
}
type Catalog {
    id: ID!
    code: String! @ id
    description: String
    segment: [Segment!] 
    releaseDate: DateTime @ search(by: [day])
}

queryCatalog(filter: {releaseDate : {le: "2021-05-01"}}, order: {desc: releaseDate}, first:1) @ cascade(fields = ["segment"]) {
    .code
     segment {
        code
     }
  }
}

Expected behaviour and actual result.

Note: Had to remove some lines from stack as you don’t allow more than 2 links

I0524 13:31:58.893450 17 http.go:240] namespace: 0. Got GraphQL request over HTTP.
2021/05/24 13:31:58 1 0

/ext-go/1/src/github.com/dgraph-io/dgraph/x/error.go:107
/ext-go/1/src/github.com/dgraph-io/dgraph/worker/sort.go:694
/ext-go/1/src/github.com/dgraph-io/dgraph/worker/sort.go:286
/ext-go/1/src/github.com/dgraph-io/dgraph/worker/sort.go:518

runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1371

2 
query {
  queryCatalog(filter: {releaseDate : {le: “2021-05-01”}}, order: {desc: releaseDate}, first:1) @cascade(fields: [“segment”]) {
    code
    segment {
      code
    }
  }
}

Try this ^. You had a few pieces of syntax incorrect if they were not just copy/paste errors.

1 Like
3

Yes, that was typing mistake.

if i sort on code, no issues, just sorting on date breaks the server.

4

I have validated that this is a bug in the latest version. Accepting as issue. @hardik to prioritize