Hi Jason,
The history behind responses looking like this is that when collections APIs
were added, the top level response to the request but nothing but a list of all
the responses from the core level admin requests that were made internally in
order to process the request. That is the reason
Hey all,
I was testing some Collections APIs the other day, and noticed a
curious response format for the SPLITSHARD and MIGRATE commands.
Both have a large number of near-duplicate responseHeader sections
with different QTimes. Is there a reason all these sections are being
returned back to
