Geir Ove Grønmo
- Total activity 292
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 124
Comments
Recent activity by Geir Ove Grønmo-
Official comment The use cases are a bit too generic. Could you please provide a more concrete use case for each of the two?
-
Official comment This has now been implemented. Before adding the first notification rule on a pipe this is shown to the user: "'Add rule' to enable Enterprise Monitoring for this pipe. Additional cost will be char...
-
Official comment We are current working on implementing this. There will be a separate "Notifications" tab on the "Subscription" page.
-
Official comment Anders's proposal is a good one. You can use the REST system to provide variable data via the entities that are processed. If that does not solve the problem, then it is probably best solved via a ...
-
Official comment We are considering adding support for incoming and outgoing converters. This would let you plug-in converters to convert to and from a non-Sesam format on the way into a pipe and on the way out.
-
Official comment 1. By the original version I assume you mean the initial version of an entity? This entity will be compacted away eventually, so there is not safe way to use this to deal with issues like this. 2. ...
-
Official comment We are investigating ways of composing microservices in various ways, e.g. pipelining and chaining. We also considering whether we should add support for doing custom conversions on incoming and ou...
-
Official comment We have added support for the "description" property on pipes, and "comment" on pipes, systems, sources, sinks and transforms. These can be single strings or an array of string. There is also the [...
-
Official comment This is generally not information we want to expose as these are implementation specific and may change. The other resources like cpu and iops are similarly not exposed. We try to reduce the memory...
-
Official comment We have recently pushed a change that causes the sink dataset to be deleted automatically when the pipe is removed (together will all other pipe state). Any orphaned datasets are also being removed...