You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EventStoreDb: in CosmosStore, BatchingPolicy/QueryMaxItems etc are de-emphasized - perhaps same should be done for the EventStore equivalents? (e.g. EventStore.Context has an overload that requires one) V4 store alignment; DeciderCore #338
replaces XXXStoreCategory.FromMemento stuff with a LoadOption.FromMemento (The system that previously used this has been decommissioned, so we may consider removing it until we have realistic use case justifying its continued existence) ResolveOption/FromMemento -> LoadOption #308 later removed
Equinox.EventStore V2 depends on EventStore.ClientApi V5.x; V3 depends on 20.6 (NOTE: EventStore Grpc and EventStore.Client 20.x require`protobuf-net 4.x whereas EventStore.Client v5.x requires protobuf-net 3.x).
Equinox.Cosmos V2 depends on Microsoft.Azure.DocumentDb.Core V2.x whereas V3 will depend on Azure.Cosmos (aka V4) targets Microsoft.Azure.Cosmos for now, as MS have parked Azure.Cosmos (aka V4) for the foreseeable
V2 supports full FW and/or netcore 1.x, with tools on 2.x, V3 tools are netcoreapp3.1
Breaking change/things that are ugly queue:
CosmosStore: will shift to usingAzure.Cosmoswhen that happens. When that work might happen is subject to change. Here's an example of some teaser info.Cosmos: Check if newer query engine optimizations might yield a better indexing strategy, see linked article in CosmosStore: Evaluate potential indexing strategy change re new query optimizations #274 (perhaps it can borrow the one that works in DynamoDB now given this enhancement?)Version(or force a full Reload?)V4 vs V3:
IAsyncEnumerablemaxAttemptsand associated throwing behavior fromDeciderctor toTransact'sattemptsargument Remove net461; target net60; reformat #310task; expose same (but retainingAsyncas the primary interface in order to avoid leaking continuation token mess) Performance: Tasks / Struct #337 V4 store alignment; DeciderCore #338EventStoreDb: inCosmosStore,BatchingPolicy/QueryMaxItemsetc are de-emphasized - perhaps same should be done for the EventStore equivalents? (e.g.EventStore.Contexthas an overload that requires one) V4 store alignment; DeciderCore #338netstandard2.1/net6.0Remove net461; target net60; reformat #310net6.0Remove net461; target net60; reformat #310"ssEvt"EventStore/SqlStreamStore: Log consistency #311Transact(interpret : 'state -> Async<'event list>)Rename TransactAsync -> Transact #314Decider.TransactAsynctoTransactRename TransactAsync -> Transact #314replaceslater removedXXXStoreCategory.FromMementostuff with aLoadOption.FromMemento(The system that previously used this has been decommissioned, so we may consider removing it until we have realistic use case justifying its continued existence) ResolveOption/FromMemento -> LoadOption #308AsyncCacheCell->TaskCell(andAsyncLazy->LazyTask) Rename AsyncCacheCell to TaskCell #432V3 breaking changes compared to V2:
will depend on Azure.Cosmos (aka V4)targetsMicrosoft.Azure.Cosmosfor now, as MS have parkedAzure.Cosmos(aka V4) for the foreseeablenetcoreapp3.1Directto match V3 SDK CosmosStore: Flip default Connection mode to Direct #281maxItemsInTipis mandatory in CosmosStoreContext ctor Cosmos: Provide a clean way to examine endpoint Uri when working from connection string #284Equinox.Cosmos V4 does not currently implement support for ignoring cert validation for e.g. use with Cosmos Simulator. NowCosmos: Port Connector bypassCertificateValidation to V3 #236 resolves this; presumably V4 will offer similar when rebasedMicrosoft.Azure.CosmosV 3.11 adds a custom HTTP factory, this could be implemented)