You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2020/11/24 07:18:00 UTC
[jira] [Updated] (IGNITE-13746) Document partition-aware data
loading
[ https://issues.apache.org/jira/browse/IGNITE-13746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-13746:
------------------------------------
Description:
Document the fact that {{CacheStore.loadCache}} discards non-primary entries, and how to deal with that properly. Old documentation has this section:
https://apacheignite.readme.io/docs/data-loading#partition-aware-data-loading
And a callout:
{code}
In case of partitioned caches and 3rd party persistence such as a relational database, keys that are not mapped to this node, either as primary or backups, will be automatically discarded.
This is not relevant for Ignite Persistent Store where every node stores only that data for which the node is either a primary or backup.
{code}
Additionally, it would be great to mention non-primary entries being discarded in CacheStore Javadoc (and .NET XMLDoc):
* https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/store/CacheStore.java
* https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core/Cache/Store/ICacheStore.cs
was:
Document the fact that CacheStore.loadCache discards non-primary entries, and how to deal with that properly. Old documentation has this section:
https://apacheignite.readme.io/docs/data-loading#partition-aware-data-loading
And a callout:
{code}
In case of partitioned caches and 3rd party persistence such as a relational database, keys that are not mapped to this node, either as primary or backups, will be automatically discarded.
This is not relevant for Ignite Persistent Store where every node stores only that data for which the node is either a primary or backup.
{code}
Additionally, it would be great to mention non-primary entries being discarded in CacheStore Javadoc (and .NET XMLDoc):
* https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/store/CacheStore.java
* https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core/Cache/Store/ICacheStore.cs
> Document partition-aware data loading
> -------------------------------------
>
> Key: IGNITE-13746
> URL: https://issues.apache.org/jira/browse/IGNITE-13746
> Project: Ignite
> Issue Type: Improvement
> Components: documentation
> Reporter: Pavel Tupitsyn
> Assignee: Denis A. Magda
> Priority: Major
>
> Document the fact that {{CacheStore.loadCache}} discards non-primary entries, and how to deal with that properly. Old documentation has this section:
> https://apacheignite.readme.io/docs/data-loading#partition-aware-data-loading
> And a callout:
> {code}
> In case of partitioned caches and 3rd party persistence such as a relational database, keys that are not mapped to this node, either as primary or backups, will be automatically discarded.
> This is not relevant for Ignite Persistent Store where every node stores only that data for which the node is either a primary or backup.
> {code}
> Additionally, it would be great to mention non-primary entries being discarded in CacheStore Javadoc (and .NET XMLDoc):
> * https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/store/CacheStore.java
> * https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/Apache.Ignite.Core/Cache/Store/ICacheStore.cs
--
This message was sent by Atlassian Jira
(v8.3.4#803005)