[
https://issues.apache.org/jira/browse/IGNITE-27938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ignite TC Bot updated IGNITE-27938:
-----------------------------------
Ignite Flags: Release Notes Required (was: Docs Required,Release Notes
Required)
> Java thin client: Configure cache paritions count
> -------------------------------------------------
>
> Key: IGNITE-27938
> URL: https://issues.apache.org/jira/browse/IGNITE-27938
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Reporter: Aleksey Plekhanov
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: ise, thin
> Fix For: 2.19
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> It's a common request from users to have an ability to configure cache
> partitions count through thin clients. The problem is: partitions count it's
> a parameter of affinity function, and affinity function is a java class.
> Technically, we have all posibilities to pass configured affinity function
> from clients to server, if affinity function/backup filter classes already on
> servers (in 99.99% cases built-in rendevois affinity function is used,
> without filters or with one of built-in filters), but this approach have some
> cons, for example it's applicable only for java thin client and it's required
> to have affinity function class on client-side.
> It's proposed to include just one parameter to ClientCacheConfiguration:
> partitions count and create default affinity function on server side with
> this partitions count. It will reduce complexity for users and will solve the
> problem.
> Currently, we also can provide custom partitions count and custom affinity
> functions by preconfiguring cache templates on server-side and using these
> templates on client-side.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
