+1 Dinesh. It will be like that. For client and server both encryption
options you can choose different key material types. I'll raise a PR soon
and you can check the tests I've.
Thanks
Maulin
On Tue, Oct 12, 2021 at 9:22 PM Dinesh Joshi
wrote:
> On 10/11/21 12:34 PM, Maulin Vasavada wrote:
> >
On 10/11/21 12:34 PM, Maulin Vasavada wrote:
Dinesh, when you say PEM and JKS formats simultaneously, do you mean that
for client vs internnode ssl we should be able to use different formats OR
beyond that within particular encryption options have a combination - PEM
based private keys and JKS ba
Blake (and Benedict), I’ll ask for your patience here. We don’t have a
precedent of pushing through major initiatives in this project in a matter
of weeks. We [members of the PMC that weren’t involved in creating Accord]
need time to do thorough research and make sure both that we understand
what
Hi Henrik,
I don't see how this resolves the fundamental problem that I outlined to
start with, namely, that without having the entire logic of the transaction
available to it, the server cannot retry the transaction when concurrent
changes are found to have been applied after the reconnaissance r
Hi Henrik,
I would agree that the local serial experience for valid use cases should be
supported in some form before legacy LWT is replaced by Accord.
Regarding your read committed proposal, I think this CEP discussion has already
spent too much time talking about hypothetical SQL implementati
Thanks Alex! I’ve hugely appreciated our exploration of the optimisation space
of Accord, and for you to have taken the time to summarise it for everyone is
particularly decent of you.
FWIW, I think there are likely some easy optimisations for providing snapshot
isolation without an initial WAN
I have, purely out of laziness, been engaging on this topic on ASF Slack as
opposed to dev@[1]. Benedict has been overly generous in answering
questions and considering future optimizations there, but it means that I
inadvertently forked the conversation on this topic. To bring the
highlights of
On Tue, Oct 12, 2021 at 11:54 PM Henrik Ingo
wrote:
> Secondary indexes are supported without any additional work needed.
>
> Correction: The "transaction reads its own writes" feature would require
to also store secondary index keys in the transaction state. These of
course needn't be part of th
Hi all
I was expecting to stay out of the way while a vote on CEP-15 seemed
imminent. But discussing this tradeoffs thread with Jonathan, he encouraged
me to say these points in my own words, so here we are.
On Sun, Oct 10, 2021 at 7:17 AM Blake Eggleston
wrote:
> 1. Is it worth giving up loca
Hi Jonathan,
You are missing the woods for the trees here. You outlined several transaction
systems, and I have demonstrated that Accord brings them *all* closer.
The immediate context of this discussion is that you are unhappy with CEP-15
due to its impact on a future transaction system. Given
10 matches
Mail list logo
