Geir Ove Grønmo
- Total activity 110
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 53
Activity overview
Latest activity by Geir Ove Grønmo-
Geir Ove Grønmo commented,
Official comment This is a good idea, but we'll probably not do it in the short term.
-
Geir Ove Grønmo commented,
We think that this is a good idea, and we'll probably implement it at some point, but currently this is not high on our list as one can work around this by materializing the subset datasets.
-
Geir Ove Grønmo commented,
Official comment This would be nice, yes. We'll look into this and see if it is possible to extract the real cause from the container runtimes.
-
Geir Ove Grønmo commented,
Official comment Have you consider using the "all" strategy and the DTL to select the one you want?
-
Geir Ove Grønmo commented,
Official comment We intend to add support for this in our service API.
-
Geir Ove Grønmo commented,
Official comment This is a good idea, and we intend to implement it.
-
Geir Ove Grønmo commented,
Do you mean "merge_datasets"? The "merge" source does not have _updated values like 629.5105.6044.44407.
-
Geir Ove Grønmo commented,
Official comment Good idea. We intend to implement this. One should be able to specify the number of consecutive pump-failed before a notification is triggered.
-
Geir Ove Grønmo commented,
The "json" sink is a sink that implements Sesam's JSON Push Protocol[1]. It follows strict rules for the payload. The "http_endpoint" receiver is symmetrical to the sink and it support entities wit...
-
Geir Ove Grønmo commented,
Official comment Being able to add custom metadata to a notification rule is a good idea. All rules currently have a name and a description field. Maybe you can encode such metadata on one of those fields for now? ...