Lucas Kent
Lucas Kent
Follow the steps at https://docs.shotover.io/examples/redis-clustering-unaware.html Rerun `redis-benchmark -h 172.16.1.2 -p 6380 -t set,get --cluster` until redis-benchmark hangs
In https://github.com/shotover/shotover-proxy/pull/406/files#diff-af55bbf1b526c4407d3c3ae203d6e081b4cc433d25e35535999723f33eaa6efc we added to_new_instance method because we needed a weaker clone. We should probably rewrite all our chains/transforms to have such a method like this instead of cloning when...
When we have optional fields that default to some value this causes a few problems: * We have to document the default value + Adds noise to the docs /...
https://github.com/shotover/shotover-proxy/pull/405#issuecomment-988554693 Add a transform configuration field named something like `return_type_on_filter` to allow the user to set the return value as either Null or Error. Ben also wanted a NoReturn option...
* Add flush handling to transforms with branching chains: Tee, ParallelMap etc. * Add flush handling to transform sinks. Previously they handled flush by default, but with the move to...
For the purposes of logging and metrics we use a name to refer to a specific transform and to specific transform chains. We want to rewrite this naming system to...
Things we want to check: * every transform chain ends in a terminating transform - complete * a terminating transform is not followed by a non-terminating transform - complete *...
get_size is completely broken, returning only the size of the value on the stack. https://github.com/shotover/shotover-proxy/blob/bc93765a20a05925bb51af81eca39697544f0278/shotover-proxy/src/transforms/distributed/tunable_consistency_scatter.rs#L78 This will require a bit of thinking on how to actually get a proper size...
This branch has working wasm plugins but requires a lot of cleanup: * shotover-proxy should depend on shotover-types crate instead of duplicating Message etc. * I designed the current implementation...