• Total activity 14
  • Last activity
  • Member since
  • Following 0 users
  • Followed by 0 users
  • Votes 0
  • Subscriptions 6

Activity overview

Latest activity by erik.leven
  • erik.leven commented,

    Yes that's the use-case. We had an issue where we needed to make sure that only a few number of all the "related" datasets needed to complete before starting the pump. In the Aker node that meant e...

  • erik.leven created a post,



    It would be really nice to have a include_completeness array available in addition to exclude_completeness. Right now, if you're downstream from a global you might have to exclude over 50 datasets ...

  • erik.leven created a post,

    Restart of system that are killed due to OOM


    Can we set a default restart of microservices that causes systems to be killed due to OOM?

  • erik.leven created a post,

    Automatically handle pipes causing OOM


    Could there be a way to handle pipes that causes e.g. OOM issues on a node? I've been involved with several projects where the whole node restarts continuously due to memory issues like "too big...

  • erik.leven created a post,

    Recursive apply-hops (not recurse)

    Not planned

    It's not possible to have an apply-hops to hop to a rule where the same rule is used in an other apply hops. I have a case where I need to created a nested list structure based on hits from an app...

  • erik.leven created a post,

    Show system connection in graph for conditional pipes with embedded data as source


    If a pipe has a conditional source with embedded data in one of the alternatives (say "test") and an sql system in an other alternative (say "prod"), for natural reasons the pipe does not show as c...

  • erik.leven commented,

    Yeah, this was regarding the merge source. Well, when I do set the "update last seen"-value through dot separation, starting with the first dataset in the datasets poperty of the source, it very of...

  • erik.leven created a post,

    Update last seen


    It would be nice with a way to update last seen for a pipe with multiple sources without having to specify every re-start point for every incoming pipe, i.e. update last seen for only one of the in...