Per my earlier suggestion, if we make the transaction id part of the activation id, and store the set of key/values associated with the transaction id in an external service (redis or couchdb) to be accessed (r/w) on-demand, then I believe the implementation can become completely transparent to "v1" / "legacy" code. However, this solution seems less performant, because of the need to access a 3rd-party service.
-- Erez From: Chetan Mehrotra <chetan.mehro...@gmail.com> To: dev@openwhisk.apache.org Date: 19/08/2019 18:37 Subject: [EXTERNAL] Re: Passing TransactionId as part of action invocation > That?s true. Time for api/v2... This is now becoming a rabbit hole! What option should we use without going for v2? 1. Introduce a new "meta" sub document 2. OR Change annotations to flat map while storing but transform that to array based structure while returning to client Chetan Mehrotra On Mon, Aug 19, 2019 at 7:15 AM Rodric Rabbah <rod...@gmail.com> wrote: > > > However changing them now would cause compatibility > > issue with various tooling out there which may be interpreting the > > annotation per current design > > That?s true. Time for api/v2... ?
