Status Update
Comments
sa...@google.com <sa...@google.com> #2
Thank you for reporting this behaviour.
I could reproduce it and forwarded it for internal investigation.
ja...@shuttlecloud.com <ja...@shuttlecloud.com> #3
I think this is the expected behavior of the Vault API count endpoint (
It's just that the Vault matters.count reference documentation does not mention that not all corpora are available for counting. Instead it mentions that the query field is a generic Query object (
After some tests, it seems the Vault API count endpoint only supports the MAIL and GROUPS corpora.
Funnily, the Vault API Guides documentation does mention this:
IMHO, the Reference documentation should be updated to refer this limitation or at least link to the Guide documentation.
lo...@google.com <lo...@google.com> #4
Hi there.
As you mentioned above, this is the expected behavior:
(Optional, supported for Gmail, classic Hangouts, and Groups) If you're worried your search will return too many results, which can take a long time to process, click Count. Count reports the number of results faster than a full search.
link
If you think the documentation can be improved, you can do it via Send Feedback
button.
Thanks for the time spent on this.
Cheers!
Description
A short description of the issue
The Google Vault API returns ahttps://developers.google.com/vault/reference/rest/v1/matters/count endpoint with the
HTTP/1.1 400 Bad Request
when using thedrive
corpus.A small code sample that reliably reproduces the issue
This is the redacted network exchange:
What steps will reproduce the problem?
What is the expected output? What do you see instead? If you see error messages, please provide them.
I expect to see the file count for the specified corpus. This endpoint works correctly for the
mail
corpus but fails for thedrive
corpus.Error returned:
HTTP/1.1 400 Bad Request