-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add API endpoint to remove a document from one folder index and add to another #55
Comments
To keep the document secondary indexing flexible my proposal would be to create an API under POST /indices/{indexType}/{operation} So in this case there would be a This would allow other types of indexing to be created with relative ease. |
@mfriesen after deleting documents (DELETE /documents/{id}), there is a list of "folders", one for each deleted document, returning on the root folder.
|
@mfriesen when moving from a folder to root, specifying "" as the target gives a 400: But when providing "/" as the target, a new folder "f#" is created in DynamoDB, and the document is moved to this folder. Based on other concepts of root that we are using, i.e., the absence of a folder being no folder ("") instead of a root of "/", I think the blank target should be admissible. In addition, the "/" folder should not be created if "/" is provided as a destination. Conversely, we can use "/" to signify root, and would also avoid creating the "/" folder. |
Also need to support adding the same file multiple times to a folder |
* #71 - Added Document Meta Data / Document Versioning * Added https://typesense.org full text search * #55 - Add API endpoint to remove a document from one folder index and add to another * #71 - Added Document Versioning DynamoDb Service * #75 - Ability to delete a folder * #74 - Fix folders index to sort folders to the top * #73 - Add ability to get a list of all tags in siteId
As folders hold a list of documents within, moving a document from one folder to another would require an API call to remove the document from the source folder and add to the destination folder.
Example endpoint:
POST /documents/{id}/move
{"sourceFolder": "Client ABC", "destinationFolder": "Client ABC/Client ABC Workspace"}
NOTE: if we want to use
move
as the resource, we can also includesiteId
in future, allowing a move between folders, sites, or both, e.g.,sourceSiteId
The text was updated successfully, but these errors were encountered: