You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Dmitriy Setrakyan (JIRA)" <ji...@apache.org> on 2015/04/06 07:45:12 UTC
[jira] [Created] (IGNITE-680) Ignite cache configuration
enhancements
Dmitriy Setrakyan created IGNITE-680:
----------------------------------------
Summary: Ignite cache configuration enhancements
Key: IGNITE-680
URL: https://issues.apache.org/jira/browse/IGNITE-680
Project: Ignite
Issue Type: Improvement
Components: cache
Reporter: Dmitriy Setrakyan
Assignee: Semen Boikov
Priority: Blocker
Fix For: sprint-3
I would like to propose additional way to configure dynamic caches, with support for wild cards.
For example, I should be able to select default config settings for all caches, with names starting from "org.mycaches.*". Then, when creating a cache, I can omit passing the configuration, and call:
IgniteCache<A, B> cache = ignite.getOrCreateCache("org.mycaches.Persons");
In this case, Ignite will find the closest configuration name, that matches the cache name, and use it.
Note, that our existing cache configuration API can already support this design:
- If CacheConfiguration has no name, then it because the default template for all caches.
- If CacheConfiguration has a name with a wild-card, then it becomes a template configuration.
- Otherwise, we should use exact name matching.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)