-
Notifications
You must be signed in to change notification settings - Fork 9
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
argus merges the data fields for duplicate names #60
Comments
This really isn't a server bug per se. It's how the Any way we would try to fix this in a server would result in inconsistent behavior from someone's point of view. Arguably, this is a client bug. It would be nice for our server software to detect it, but that's not really feasible given the current state of things. |
Spoke to @ilawjr and he recommended to document this in our readme as a heads up. |
Currently, Argus accepts json payloads with duplicate object names e.g.
{"identifier" : "minimal0","data": {"minnie":"mouse"},"ttl":300,"identifier" : "minimal1","data": {"mickey":"mouse"},"ttl":600}
This is what's stored:
{"identifier":"minimal1","data":{"mickey":"mouse","minnie":"mouse"},"ttl":572}
Non-unique names appeared to be allowed in json, but this results in inconsistent behavior. The value for identifier & ttl are replaced by the later duplicate, but data field values are merged.
The text was updated successfully, but these errors were encountered: