[
https://issues.apache.org/jira/browse/IGNITE-16603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey N. Gura updated IGNITE-16603:
------------------------------------
Description:
One of the most important capabilities that Apache Ignite provides is the
ability to colocate. There are two aspects of colocation:
# Data colocation, i.e. grouping entries together based on a certain criteria.
# Compute colocation, i.e. sending a computation to a node where a particular
set of data resides.
Also Apache Ignite 1.x/2.x uses the term _affinity key_ and a user must use
affinity key in order to colocate the data. Because the main goal is data
colocation, the user should not operate by affinity key term. Instead, the
_colocation_ term should be used directly.
See IEP-86 for details:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-86:+Colocation+Key
was:Ignite 3 should support data colocation.
> Support of colocation in 3.0
> ----------------------------
>
> Key: IGNITE-16603
> URL: https://issues.apache.org/jira/browse/IGNITE-16603
> Project: Ignite
> Issue Type: Epic
> Reporter: Yury Gerzhedovich
> Priority: Major
> Labels: iep-86, ignite-3
>
> One of the most important capabilities that Apache Ignite provides is the
> ability to colocate. There are two aspects of colocation:
> # Data colocation, i.e. grouping entries together based on a certain
> criteria.
> # Compute colocation, i.e. sending a computation to a node where a
> particular set of data resides.
> Also Apache Ignite 1.x/2.x uses the term _affinity key_ and a user must use
> affinity key in order to colocate the data. Because the main goal is data
> colocation, the user should not operate by affinity key term. Instead, the
> _colocation_ term should be used directly.
> See IEP-86 for details:
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-86:+Colocation+Key
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
