My application use client version 4.04 and server 3.7.5.1 and tools is 3.7.5.but I try
another aql command and it shows the right bin content like follows:
aql> execute llist.scan(‘list’) on pub-sub.Object where PK = ‘’/pub/com/servlet/c1/1597865255’’
±---------------------+
| scan |
±---------------------+
| [“1342286016/16258”] |
±---------------------+
1 row in set (0.000 secs)
I really have no clues what makes the difference of the command.
I find Large List command like “execute llist.scan(‘LLIST_BIN’) on test.demo where pk = 'Key_1”,which is used to query bins of single LDT record.But I donot find the Large List command which is used for querying one namespace.
Is there a command for querying the bins of the whole namspace?
LDTs are data structures existing within a single bin on a record, accessed via record UDFs as in your example.
There are no AQL features for operating on LDTs across records, at the set or namespace level. This is an intentional design limitation, but not a bug.
I got it,but I still wonder we try “Select” on 3.6 and 3.5 version server and we got the right value of bins of LDT.but we try the query on 3.7.5.1,We got the bins of LDT are null.Is this coincidence or something changed?
With python client,the similiar situation is met.
python client code like follows:
def QueryData(self ,namespaces=namespaces ,set=set):
res = self.client.query(namespaces ,set)
return res.results()
On sever 3.6 version ,it can show the right value of Bins of LDT .
however, 3.7.5.1 It shows bins of LDT as null.
It seems to me that both results should return null.
From the release note,I saw the two updates on scan option in server 3.7 and python client 2.0,Are these updates make query results different.
[AER-3789] - (Scan) Add option to include LDT data in scans.
[CLIENT-609]Added the scan option include_ldt.