LDT detached from record in AQL


#1

Hi,

Along our usage of aerospike, we encountered something strange using the AQL tool. It appears that under some circumstances the LDT is detached from the record it is associated to. The following snippet shows what I try to explain and also that there are two records in the bin, rather than one with an LDT:

aql> select * from test.test_dummy
+---------------+-----------------------------------+-------------+
| LDTCONTROLBIN | data                              | key         |
+---------------+-----------------------------------+-------------+
|               | [{"value":"llist", "key":"test"}] |             |
|               |                                   | "dummy_key" |
+---------------+-----------------------------------+-------------+
2 rows in set (0.090 secs)

When this occur, it is impossible to access the LDT using the record as the following error is triggered (I am using here the Python Aerospike Client Library):

exception.LDTBinNotFound: (1417L, 'LDT-Bin Does Not Exist', 'src/main/llist/llist_operations.c', 400)

Is this a normal behaviour? Is there a way to access these llist and delete them?


#2

@jgrosse,

Thank you for posting about LDTs in our forum. Please see the LDT Feature Guide for current LDT recommendations and best practices.


#3

@jgrosse,

Effective immediately, we will no longer actively support the LDT feature and will eventually remove the API. The exact deprecation and removal timeline will depend on customer and community requirements. Instead of LDTs, we advise that you use our newer List and SortedMap APIs, which are now available in all Aerospike-supported clients at the General Availability level. Read our blog post for details.