Headers no longer available in 1.10.0

I just upgraded from 1.8.0 to 1.10.0 and the headers are no longer returned in this query: client.queryDocuments(collectionLink, querySpec, options).toArray((err, items, headers) => {

I had a look in the code and don’t understand the logic completely, but it seems to recursively iterate over the results and overwrite the headers in the second recursion: https://github.com/Azure/azure-documentdb-node/blob/master/source/lib/queryIterator.js#L144

Added a quick patch to validate that headers are defined which solved the issue, but I don’t think this is the ideal solution. Is there a reason to recurse over the results? Is it that the iteration may trigger additional server requests?

[moderakh]

@saibotsivad we will support returning request charge if you use queryIterator.executeNext(callback(err, resources, headers)) In case of a cross partition query headers will at least have the request charge.

Feel free to send a PR for updating the documentation for executeNext(.) saying that headers will accessible as the third arg.

[saibotsivad]

@moderakh Previously this issue was marked as closed because it was a “non-documented feature”. I still don’t see the headers as being a documented returned property, so even if it works now with the latest version of documentdb it doesn’t sound like there is any guarantee that it will work in the future.

Do you know if there is an intent to document the headers in the queryIterator.executeNext method at some point? I imagine that might take a while?