[ 
https://issues.apache.org/jira/browse/IGNITE-21425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Julia Bakulina updated IGNITE-21425:
------------------------------------
    Description: 
Let's correct several mistakes in Data Modeling examples in Apache Ignite docs 
- https://ignite.apache.org/docs/latest/data-modeling/affinity-collocation.

- remove 'companyId' from AffinityCollocationExample.class
- replace 'cityId' with 'id'
- replace 'companyId' with 'name'
 -replace 'company1_key' with 'company1'
- replace CacheConfiguration<AffinityKey<Integer>, Person> with 
CacheConfiguration<AffinityKey<PersonKey>, Person>



  was:
Let's correct several mistakes in Data Modeling examples in Apache Ignite docs 
- https://ignite.apache.org/docs/latest/data-modeling/affinity-collocation.

- remove 'companyId' from AffinityCollocationExample.class
- replace 'cityId' with 'id'
- replace 'companyId' with 'name'
- replace CacheConfiguration<AffinityKey<Integer>, Person> with 
CacheConfiguration<AffinityKey<PersonKey>, Person>



> Update examples in Data Modeling - Affinity Colocation
> ------------------------------------------------------
>
>                 Key: IGNITE-21425
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21425
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Julia Bakulina
>            Assignee: Denis Polozhaev
>            Priority: Major
>              Labels: ise
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Let's correct several mistakes in Data Modeling examples in Apache Ignite 
> docs - 
> https://ignite.apache.org/docs/latest/data-modeling/affinity-collocation.
> - remove 'companyId' from AffinityCollocationExample.class
> - replace 'cityId' with 'id'
> - replace 'companyId' with 'name'
>  -replace 'company1_key' with 'company1'
> - replace CacheConfiguration<AffinityKey<Integer>, Person> with 
> CacheConfiguration<AffinityKey<PersonKey>, Person>



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to