Feature/delete points by source

[AlboCode]

Description

Add an endpoint to delete points based on source, which potentially can be expanded to filter delete by all the metadata properties.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas

[zAlweNy26]

Looks good, but please update the description here on the issue 😊

[AlboCode]

@zAlweNy26 Done

[giovannialbero1992]

Hi all, any chance to see this PR merged? :-)

[pieroit]

Hi @AlboCode @giovannialbero1992 yes will be merged soon (little busy with version 1.1 on branch develop, coming soon ;)

[giovannialbero1992]

great to hear that! 😄

[pieroit]

Also, there should be a test for this (under tests/routes/memory/

[pieroit]

@AlboCode merged your commits into develop thanks

@AlboCode @giovannialbero1992 I made the endpoint more general for other metadata

metadata = {
    "source": "sample.pdf"
}
client.request("DELETE", "/memory/collections/declarative/points", json=metadata)

Also check the tests about the endpoint here

This can do for the moment, problems:

• DELETE verb should not support a JSON
• the whole CRUD and filtering about points should be designed top down, in order to make it flexible enough for many use cases (if you would like to make a proposal, you are welcome - let's draft the endpoints in an issue)

Thanks

[giovannialbero1992]

Thanks @pieroit