
Geir Ove Grønmo
- Total activity 255
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 0
- Subscriptions 108
Activity overview
Latest activity by Geir Ove Grønmo-
Geir Ove Grønmo commented,
Official comment Agreed. We'll also add support for string arguments to the `ni-ns` function as it is similar.
-
Geir Ove Grønmo commented,
Official comment Rescans use the same logging logic as all full syncs. They only log pump runs if there were actually any changes. You can opt-out of the default behaviour by setting `log_events_noop_runs` and `log...
-
Geir Ove Grønmo commented,
Changelog: https://docs.sesam.io/changelog.html#changelog-2022-10-11
-
Geir Ove Grønmo commented,
We just merged warnings for pipes where dependency tracking won't be done or guaranteed. In practice you'll see it on non-dataset sources that has hops or pipes with hops in the non-first transform.
-
Geir Ove Grønmo commented,
Official comment We have had discussions about how to improve the pipe progress status in the UI. This is a fairly major effort, but it is clearly something that would be very useful. We intend to make improvements...
-
Geir Ove Grønmo commented,
Official comment Indeed. It it unnecessary to retry requests that returned 4xx as these are client side problems. We'll look into how we can handle this.
-
Geir Ove Grønmo commented,
Official comment Yes, we already have this on our planning board. We'll add a warn to pipes where hops are used, but dependency tracking won't be guaranteed or done. Another example is if the pipe source is not a ...
-
Geir Ove Grønmo commented,
Official comment The "Graph" tab on a pipe will let you see what related datasets are unpopulated. You could then traverse the graph upwards or side-ways to identify the dataset(s) that cause the lack of propagatio...
-
Geir Ove Grønmo commented,
Official comment We already have support for this in the backend, but it works on the subscription level. It should definitely be made available in the UI as well.It is not possible to support this on the system le...
-
Geir Ove Grønmo commented,
This has now been implemented. You can find the outbound IP in the Management Studio under Subscription > Network > Firewall.