[
https://issues.apache.org/jira/browse/IGNITE-7288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304289#comment-16304289
]
Vladimir Ozerov commented on IGNITE-7288:
-----------------------------------------
[~ptupitsyn], my comments:
1) Do we really need {{invalidate}} flag? AFAIK it is used only for near
caches, but do we support their creation from the client?
2) It is better to group properties, so that the most important things are on
the top. E.g.:
{code}
/* !!! */
Name
/* The most common properties */
CacheMode
AtomicityMode
Backups
WriteSynchronizationMode
CopyOnRead
ReadFromBackup
/* Persistence and page memory */
DataRegionName
OnheapCacheEnabled
/* SQL stuff */
QueryEntities
QueryParallelism
QueryDetailMetricsSize
SqlSchema
SqlIndexMaxInlineSize
SqlEscapeAll
MaxQueryIteratorsCount
/* Rebalance */
RebalanceMode
RebalanceDelay
RebalanceTimeout
RebalanceBatchSize
RebalanceBatchesPrefetchCount
RebalanceOrder
RebalanceThrottle
/* Advanced */
GroupName
KeyConfiguration
DefaultLockTimeout
MaxConcurrentAsyncOperations
PartitionLossPolicy
EagerTtl
StatisticsEnabled
{code}
> Thin client: partial cache configuration
> ----------------------------------------
>
> Key: IGNITE-7288
> URL: https://issues.apache.org/jira/browse/IGNITE-7288
> Project: Ignite
> Issue Type: Improvement
> Components: thin client
> Affects Versions: 2.4
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Fix For: 2.4
>
>
> {{OP_CACHE_CREATE_WITH_CONFIGURATION}} and
> {{OP_CACHE_GET_OR_CREATE_WITH_CONFIGURATION}} should not require complete
> {{CacheConfiguration}}. User should be able to specify any combination of
> properties in any order, leaving others at default state.
> Prefix each property with unique ID, then do a switch in a loop.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
