These are chat archives for atomix/atomix
get. The reason there's no
keySettype methods is to avoid pulling the entire map to the client. There's been some debate about whether or not this should be implemented. I'm not particularly opposed to it considering that data structures are not partitioned in any way and are therefore limited to the size of a single node anyways. The alternative is lazy
Setimplementations and/or lazy implementations of the Java 8 stream API, but there are consistency and memory issues to consider with those. In order to properly manage a lazy collection we'd probably have to copy the memory on the server. Many concurrent iterators could consume a lot of memory. But I don't want to mess with that stuff now. We'll likely just implement them as a single request/response that would be limited by the Netty frame size and handle the resource issues in a later version.