Jesse Benson

Results 10 comments of Jesse Benson

Yes, this is definitely a Service Fabric issue. I believe that Service Fabric has a max size on transactions. The error message and user experience they provide for this is...

That is interesting. What is the size of your main items, and what are the indexes you are using? Service Fabric has a max size on transactions and/or if transactions...

Let me understand the request. Do you want FilterableIndex to have a unique key, such that if you try to insert another item with that same key it should fail...

Hey @Anu666, one workaround is to use the underlying `IReliableIndexedDictionary` interface directly, which allows you to pass in your transaction. LINQ is a built-in C# language feature, so there's no...

Yeah ... this was always a gap. In my mind, there's two ways to do this: [1] Add an API to `IReliableIndexedDictionary` like `RebuildIndexAsync()`, which will enumerate the values in...

I was suggesting using the same dictionary, something like below: ``` var dict = await stateManager.GetAsync("dict-name"); var index = await stateManager.GetIndexedAsync("dict-name"); for ((key, value) in dict) { using (var tx...

The current code cannot be used directly to query all Actor states, as it is Reliable State Manager specific. A similar mechanism _could_ be used to query Actor states via...

Note that to use this extension, you must use the Queryable dictionary when adding/updating/removing entries to the dictionary (i.e. use `queryableDictionary` and not `dictionary` in your code above). Otherwise, the...

The LINQ implementation was a contribution. I suspect the LINQ implementation is not complete. You can see and attempt to fix the code here: https://github.com/jessebenson/service-fabric-queryable/blob/master/src/ServiceFabric.Extensions.Services.Queryable/LINQ/ReliableIndexedDictionaryQueryContext.cs The alternative is to use...

The OData syntax is just a particular string format (no need to include OData packages/etc.) on how you structure the queries - i.e. rather than using LINQ. It's something to...