Secondary index scan limitations under strong consistency quorum

Aerospike provides strong consistency for key‑value operations through namespace‑level read and write quorum settings. When these are set to all or majority, the system ensures linearizable reads for direct key accesses by coordinating across replicas.

However, secondary index scans do not appear to honor these same namespace‑level quorum configurations. Even when a namespace is configured for strong consistency, queries involving secondary indexes may bypass the quorum logic, potentially returning stale data or inconsistent results during network partitions.

Is there a configuration method to enforce read‑quorum requirements specifically for secondary index scans? How does the system maintain consistency guarantees when a scan encounters a replica that is behind the required quorum?