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

Ensure the consistency of signal enrichment for connections #1893

Closed
kyberpunk opened this issue Feb 5, 2024 · 1 comment · Fixed by #1904
Closed

Ensure the consistency of signal enrichment for connections #1893

kyberpunk opened this issue Feb 5, 2024 · 1 comment · Fixed by #1904
Labels
Milestone

Comments

@kyberpunk
Copy link
Contributor

Hello. I have a specific case where I use following connection topic _/_/things/twin/events?extraFields=features/{{feature:id}},thingId&filter=like(resource:path,'/features/SoftwareUpdate*') to consume change notifications by stateless service, which are enriched for other contextual data from the same feature even in case of partial feature modification. Currently it happens in case of concurrent modify commands, that extra field contains different values than actual changes in value field (see screenshot).

Since ditto supports retrieving historical revisions, the proposal is to provide deterministic and strong consistency by not looking up the current state, but the state at the revision number of the processed event. However, in some other use cases it may be more efficient to keep the caching implementation.

Thank you.

ditto-mismatch-between-value-and-extra-status_ditto-twin-software-update-topic

@thjaeckle thjaeckle added the bug label Feb 5, 2024
@thjaeckle thjaeckle added this to the 3.5.3 milestone Feb 5, 2024
@thjaeckle
Copy link
Member

I try to take a look soon.

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

Successfully merging a pull request may close this issue.

2 participants