Doubts about record.bin_names and geojson. about aerospike-mod-lua

[bwhisler]

We'd like to better understand these aerospike.null() bins. Are records being written by the Python client with a bin value of aerospike.null() and stored in the database? And then the client reads the record back and finds a bin with an aerospike.null() value in it? This seems odd, as we'd expect that writing a bin with a null value would delete the bin. How exactly are these records being written? Knowing this I think we could determine why a UDF would not see the bin and perhaps make an adjustment as needed.

Regarding GeoJSON, there are currently no plans to add support for Geo queries in UDFs.

[vVv-AA]

@bwhisler Sorry for the jumping the gun here. I rechecked the code. It is working as intended. aerospike.null() is not returned. When reading the bins, there was a default value being passed in some part of the code. Missed that part. Closing the issue. Thanks.

I also, misunderstood the as_bin_inuse then. Since the null bins are not stored, what do AS_PARTICLE_TYPE_NULL and AS_BIN_STATE_UNUSED correspond to?

[bwhisler]

Both AS_PARTICLE_TYPE_NULL and AS_BIN_STATE_UNUSED are used internally to help manage a bin array as a record is being processed. We'll typically allocate an (oversized) array of bins when processing a record, and those NULL/UNUSED constants help indicate how much of the internal bin array is actually needed to handle the record in question.