-
Notifications
You must be signed in to change notification settings - Fork 218
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 support for twin life-cycle events #898
Comments
This makes sense, yes. Regarding syntax: we would have to support it in the RQL queries, some ideas:
|
For the features part, nice addition! I could think of RQL queries for those like this So I'm currently further tracking life cycle states which might be really use-case dependent and not that helpful for a general implementation. Would have to think about that a bit more first, but here you go:
I agree that property/attribute level events seem to be a bit over-kill |
Hi, in our systems, we have a period of calibration validity (in german "Eichgültigkeit") in our lifecycle. Maybe, a "OUT_OF_GUARANEE" makes also sense.
|
Hi @thlandgraf |
We start working on this issue.
Targeted is only the lifecycle of the thing/twin (as the title of the issue also suggests), feature lifecycle is out of scope for this issue. |
…it is now a transitive dependency of ditto-protocol * enhanced RunOSGiContainerIntegrationTest to test loading a "ditto-placeholders" class * update logback to 1.2.6 Signed-off-by: Thomas Jaeckle <thomas.jaeckle@bosch.io>
…termine the TopicPath for a given Signal * move "instanceof" cascade to DefaultAdapterResolver to make it reusable * simplified DittoProtocolAdapter, removed non-needed overloaded methods * added SignalMapper implementations for ThingEvents and extracted the payload adding behavior for events to them * added SearchErrorResponseAdapter Signed-off-by: Thomas Jaeckle <thomas.jaeckle@bosch.io>
…ic module "ditto-placeholders" * make use of PlaceholderResolver in RQL ThingPredicateVisitor et. al * move TopicPathPlaceholder from connectivity internals to "ditto-protocol" * instantiate TopicPathPlaceholder with extracted TopicPath at places relying on RQL filtering Signed-off-by: Thomas Jaeckle <thomas.jaeckle@bosch.io>
Signed-off-by: Thomas Jaeckle <thomas.jaeckle@bosch.io>
…st be Java 8 compatible Signed-off-by: Thomas Jaeckle <thomas.jaeckle@bosch.io>
* optimized DefaultAdapterResolver to take less "instanceof" checks * removed static addition for "topic:action" again from ThingsFieldExpressionFactoryImpl, this is not required * made previously public methods in FieldExpressionUtil package private and exclude from API compatibility breakage Signed-off-by: Thomas Jaeckle <thomas.jaeckle@bosch.io>
…h "topic:action" for modified events and "topic:subject" for filtering live messages * fixed found bug in Thing3ValuePredicateVisitor * also apply filtering for non ThingEvents (e.g. live messages), but with empty thing Signed-off-by: Thomas Jaeckle <thomas.jaeckle@bosch.io>
…using RQL property "topic:" and "resource:" Signed-off-by: Thomas Jaeckle <thomas.jaeckle@bosch.io>
…ocumentation with "{{ }}", but plain Signed-off-by: Thomas Jaeckle <thomas.jaeckle@bosch.io>
[#898] Add filtering for "topic:" and "resource:" placeholders in RQL expressions
In order to integrate other components and services of an infrastructure for some use-cases it's crucial to act on life-cycle events of a twin. E.g. to register the twin on it's creation with monitoring, etc. Or to de-register when it is decommissioned.
Therefore the connectivity, HTTP and websocket APIs need means to filter for those events only. Otherwise one would have to listen on a potentially large data stream to manually fish out life-cycle events.
There is certainly even more potential in this concept, so let's discuss!
The text was updated successfully, but these errors were encountered: