DELETE Document API does not work unless a corresponding file exists in S3 #44
Milestone
Comments
mfriesen
pushed a commit
that referenced
this issue
Sep 23, 2022
mfriesen
added a commit
that referenced
this issue
Sep 25, 2022
* #44 - DELETE Document API does not work unless a corresponding file exists in S3 * #40 - Add last modified to GET documents and GET document/{id} * #45 - Metadata records with no corresponding S3 object are causing issues on GET /documents * #46 - 500 Error in /search endpoint when using large "limit" with "responseFields" * #48 - File downloads are named using the document ID rather than the original filename * added POST /documents/{documentId}/actions * POST /searchFulltext - added pagination
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you use the Document POST API to create a new document record, but do not use the resulting URL to actually upload the file to S3 (or if this operation fails), the original Document record cannot be deleted using the DELETE Document API. The response is "Document {GUID} not found."
The text was updated successfully, but these errors were encountered: