THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
| ID | IEP-86 |
| Author | |
| Sponsor | |
| Created |
|
| Status | DRAFT |
| Table of Contents |
|---|
Motivation
...
The affinity key mapper in Apache Ignite 1.x/2.x allows to implement some user defined logic for data colocation. Any user’s code is a potential problem because it leads to code deployment/redeployment issues, to error prone approach, etc. Instead of the affinity key mapper interface Apache Ignite 3 should provide the possibility to use a predefined set of SQL functions in the COLOCATE BY clause (see for example PARTITION BY clause in different databases).
Open Tickets
| Jira | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Closed Tickets
Jira server ASF JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,customfield_12311032,customfield_12311037,customfield_12311022,customfield_12311027,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,Priority,Priority,Priority,Priority,priority,status,resolution maximumIssues 20 jqlQuery project = IGNITE AND (labels = iep-86) AND status IN (resolved, closed) serverId 5aa69414-a9e9-3523-82ec-879b028fb15b
Overview
Content Tools
Apps