[ https://issues.apache.org/jira/browse/IGNITE-20360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17804662#comment-17804662 ]
Mirza Aliev commented on IGNITE-20360: -------------------------------------- Merged to feature branch `*storage-profiles-feature`* > Implement the set of zone supported storages > -------------------------------------------- > > Key: IGNITE-20360 > URL: https://issues.apache.org/jira/browse/IGNITE-20360 > Project: Ignite > Issue Type: Task > Reporter: Kirill Gusakov > Assignee: Mirza Aliev > Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > *Motivation* > According to IGNITE-20357 we need to have an appropriate zone filter, which > filters the nodes based on their available storages. > *Example* > {code} > create zone z1 with storage_profiles="lru_rocks,*clock_aipersist"; > {code} > As a result:: > * Zone consists of nodes which supports the *BOTH* storage profiles > lru_rocks and clock_aipersist > * Default storage profile for this zone will be clock_aipersist, because it > is marked with *. It means, that (after the IGNITE-20361) if on table > creation we will skip the storage profile for table: > {code} > create table t1 using zone="z1"; > {code} > the table t1 will use clock_aipersist storage_profile. > *Definition of done* > * Zone has the filters, which can be unambiguously used to check if table > can be "deployed" in this zone > *Notes* > * Avoid filter altering for now (but add the appropriate event types) > -- This message was sent by Atlassian Jira (v8.20.10#820010)