Null handling in apoc.coll.sortMaps/sortMulti differs to ORDER BY

[Reiner (Clooney24)]

Hi,

I was surprised that handling of null values is not the same using ORDER BY compared to apoc.coll.sortMaps/apoc.coll.sortMulti. Is this by intent? (using Neo4j Enterprise 4.4.2)

with [{prop:null}, {prop:1}, {prop:2}] as items
unwind items as item
with *
order by item.prop 
with collect(item) as itemsOrderedBy,
    apoc.coll.sortMaps(items, '^prop') as itemsSortMaps,
    apoc.coll.sortMulti(items, ['^prop']) as itemsSortMulti
return *

Best,
Reiner