You should configure server nodes, not clients for that, if you use C# servers, so see IgniteConfigurationSection.xsd for that. Using it you can specify cache name and expiryPolicyFactory for any cache.
Best Regards, Igor On Mon, Jul 16, 2018 at 10:37 PM ysc751206 <yung751206.ec...@g2.nctu.edu.tw> wrote: > Does that mean we can only support one expiry policy? In our application, > depending on the situation, some of cached object use absolute expiry > policy > but some of them may use sliding expiry policy. If it is possible to create > many cache with different expiry policy, how to get them from thin client? > > Based on schema IgniteClientConfigurationSection.xsd, I am not sure how to > specify which cache I want to use. There is no field to specify cache name. > > If there is no workaround to support different expiry policies, is there a > plan to support it in the near feature? > > Thanks, > Edison > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
