Skip to content
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

[Feature Request] One document Endpoint #1494

Open
zaterio opened this issue Dec 14, 2022 · 1 comment
Open

[Feature Request] One document Endpoint #1494

zaterio opened this issue Dec 14, 2022 · 1 comment

Comments

@zaterio
Copy link

zaterio commented Dec 14, 2022

Hi @nicolaiarocci,

Too many times I have needed an endpoint to be used as a configuration point for other applications, for example:

schema_transcoding_config = {
'encoding_enabled': {'type': 'boolean', 'default': True},
'threads': {'type': 'int', 'default': 1},
}

endpoint only needs one item, and old ones are deleted periodically.

I suggest the following new feature: At the endpoint level, a new setting "one_document_endpoint" (for example): An endpoint configured with "one_document_endpoint", must ensure that only one document is kept, in case of Create/Update Document, old documents must be deleted. DELETE operations on Collection/Document not allowed, Bulk operation not allowed.

Please consider whether this feature is appropriate.
I am a volunteer for its implementation.

Thanks!

@nicolaiarocci
Copy link
Member

Hi @zaterio. All of this would be attainable, I think, with some 'maintenance activity' on the client side. Like, only send update commands to the single document originally stored at the endpoint. I understand the usefulness though, especially around avoiding unwanted behavior on behalf of rogue (or bugged) clients. Is this the only reason you would want the feature added?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants