Maksim, ClientRendezvousAffinityFunction is an implementation of AffinityFunction interface? If not, API will be inconsistent again, but much more complicated. If yes, why do we need additional layer instead of using standard affinity? How and where it will be mapped to a real affinity function? How does this change affect protocol? What fields should be added? In case of standard affinity - one object field can be added (binary representation of affinity) in case of partitions count - one int field can be added. In case of a new entity how will we serialize it? What if the user provides their own implementation? How will it be mapped to real affinity?
For me it brings a lot more inconsistency than any of the solutions mentioned before. чт, 5 мар. 2026 г. в 13:54, ткаленко кирилл <[email protected]>: > > Hi. > > We can make the approach even more flexible by passing cache creation > parameters as Map<String, String>. Define an affinity function creation > handler on the server side and configure it, for example, in > IgniteConfiguration or as a plugin. By default, an affinity rendezvous will > be created with all the necessary parameters. > > Wdyt?
