DQL upper limit

Users Dgraph
1

Hi, is there any upper bound of DQL in one single query? I want to count the amount of 3-hop user connect to this uid list, as shown below:

{ var(func:uid(0x3b4baff45b09bf2,0x835bc27c5480ce8,0x93d263491b49ada,0xf43ff1d06a2e5c0,0x13bae7702ff5fd75,0x1745657e43dbdb26,0x184ee333b959829e,0x1a04e21400f7b216,0x1ce326bb82a353b0,0x1ddad607398fe87c,0x1f6fa75010883814,0x2530eb021be47efc,0x29c97be1a86293f0,0x326e3fb8ec3429ab,0x3462a783bd710481,0x367b98e8a05dd6a8,0x44700ab1914bf576,0x46b33fde7dbfc7c2,0x4910b1966ef7c7aa,0x555b51de3d667dbc,0x5b7ef7d4377dbc8f,0x5b9728da95464cc8,0x5c8a1deada1f46eb,0x5d30f69a0e21c90b,0x5f1d9aaf218bd5c4,0x60dc66f9dfe97d6d,0x645970e7e63c440a,0x651bf4c30e7c5056,0x6a85c7058a571484,0x6b4622094fe3b599,0x6dc6aaa80659eba3,0x77e1b234d4562c33,0x7dac975f9c40b922,0x803daa80bbc4e1cc,0x85edbed8b9e76f76,0x8b0b094162e131b5,0x95338ea25db6daae,0x972fe8f2a6781718,0x9a080346bf290b4f,0x9ee0a2a475860e84,0xa162994f1283a188,0xa46851d4964dd35f,0xa504a9887474f8be,0xa6176f4ab185d469,0xa770fb15dd64f1c3,0xa796aef749989af9,0xab58478d395caee0,0xabd4faada27cb99b,0xafb0eb0a263f3aed,0xb0501a6238176f92,0xb060d59873ac7495,0xba8deb4f16ef3011,0xbf8dd2b6948f3925,0xc1b2ba0f0020e601,0xc2da787eab3313a1,0xca97a4b0b92cd7e2,0xcd5e6aecb76d9267,0xceea48bae6335a55,0xd0719dc6ddcd4cf0,0xde19ea83ea94ddb7)) {    
    ~click  {  
      ~log_id{a1 as uid}
    }
  }
  var(func: uid(a1)){u1 as count(uid)}

  q(){
    all_u1 : sum(val(u1))
  }  
}

result:

image
image1436×664 31.5 KB

All looks good, but when I add one or more uid into this list, query return nothing:

image
image1807×557 29 KB

This single uid is fine:

image
image1829×711 27.3 KB

Alpha command:
nohup ./dgraph alpha -p=/data/p_dir/p_d3 -w=/data/p_dir/w3 --my=xxx:7082 -o=2 --zero=xxx:5080 --query_edge_limit=10000000000 --idx=3 --whitelist=xxx --cache-mb=20480 --normalize-node-limit=10000000000 --snapshot-after=1000000 &

Data contain:

node_start: 7.8GB
log_id : 106G
click: 438M
node_end: only 700
schema follows: node_start -> log_id -> click  -> node_end
2

Solve it, this maybe is a problem of dgraph-ratel, this issue didn’t show up when used pydgraph or dgraph4j client.