The usage in the trie memtable is only for volatile access to buffers. In
this case I chose the library instead of reimplementing the functionality
(e.g. as methods in `ByteBufferUtil`) because the relevant interface makes
sense and the library is a good quality one that contains a range of other
u
Vote passes with eight +1s (seven binding) and no vetos.
Thanks everyone.
On Thu, 22 Sept 2022 at 20:50, Josh McKenzie wrote:
> +1
>
> On Thu, Sep 22, 2022, at 4:28 AM, Mick Semb Wever wrote:
>
>
>
> I'd like to propose CEP-20 for approval.
>
> Proposal:
> https://cwiki.apache.org/confluence/di
I think that custom, pluggable type of guardrail will be a great addition
to the framework.
The first guardrails prototype included a factory of guardrails that was
able to provide different guardrail instances depending on the specified
class and client state. That was discarded during review in
+1 from me
> On Sep 23, 2022, at 1:21 AM, Branimir Lambov
> wrote:
>
> The usage in the trie memtable is only for volatile access to buffers. In
> this case I chose the library instead of reimplementing the functionality
> (e.g. as methods in `ByteBufferUtil`) because the relevant interface m
