Matthias Wahl

This is the RFC for this: https://github.com/tremor-rs/tremor-rfcs/pull/46

To make matters worse, there is a new instance of both `codec` and `postprocessor` or `preprocessor` created for every new stream.

When we have Troy, we can control this via the connect statement: ``` connect "connector/my_tcp/instance" to "/pipeline/foo/instance", "/pipeline/foo/instance" with gd=at_least_one; ``` where possible values for `gd` are `always`, `require_all` and...

My 2 cents for the lookups: Defaulting only applies to nested paths, that is paths like `a.b` or `a["b"]` or `a[42].b`. And it is the nesting that can fail at...

When it comes to filling a struct with default values the approach that appeals to me the most is the `patch` operation `default` which works with both single keys and...

First step would be to add an opensearch integration test in `tremor-cli/tests/integration`. It can be heavily based on the `elastic` test in there. Whatever client library we then chose to...

We definitely need functions for producing timestamp strings (there are two RFC formats for this), as e.g. the google bigquery connector requires timestamp strings.

UUIDv4 suffices for starters. This is the most useful and widely used. A string could be parsed to its 128 bit number or (if we dont support this out of...

We use the official client now.

`rustls-native-certs = 0.6.1` supports rustls 0.20.