Open AndersSahlin opened 9 years ago
This one is a bit ugly. The JVM Api is designed around long values for journal sequence numbers, which is all fine. In our specific implementation here, there are two issues;
int.Max
entries from servicefabric. as that would probably take a couple of days and a bizarre amount of memory to deserialize such object.So, are we OK with the long to int truncation?
cc. @clca
It is probably a corner case considering that it would assume that an Actor would need 100s GB of storage for its state. We may want to catch this case at the plug-in level and return some sort of error.
The read count is truncated from Long to Int. Document this behavior.
In
ServiceFabricPersistence.ServiceFabricEventJournal.GetMessagesAsync
int m = max > int.MaxValue ? int.MaxValue : (int)max;