Possibe behaviour with Aerospike Java client, Statement.setMaxRecords when it's set to 1

Hi, For version info, using the aerospike client version: 9.0.5 (jdk21 version) From reading the javadoc, it states the following for the Statement.setMaxRecords() method:

Set maximum number of records returned (for foreground query) or processed (for background execute query). This number is divided by the number of nodes involved in the query. The actual number of records returned may be less than maxRecords if node record counts are small and unbalanced across nodes.

For the part about the actual number of records being less, does that apply when the value is set to 1? ie. Is it possible in a multi node cluster that such a query returns 0 records if setMaxRecords(1) is specified?

Thanks