Repository: ignite Updated Branches: refs/heads/master 42b8000c7 -> 285644ae5
minor - fixed javadoc Project: http://git-wip-us.apache.org/repos/asf/ignite/repo Commit: http://git-wip-us.apache.org/repos/asf/ignite/commit/285644ae Tree: http://git-wip-us.apache.org/repos/asf/ignite/tree/285644ae Diff: http://git-wip-us.apache.org/repos/asf/ignite/diff/285644ae Branch: refs/heads/master Commit: 285644ae597a49c25a84c21c2601729e40459c38 Parents: 42b8000 Author: Yakov Zhdanov <[email protected]> Authored: Mon Jun 26 13:46:33 2017 +0300 Committer: Yakov Zhdanov <[email protected]> Committed: Mon Jun 26 13:46:33 2017 +0300 ---------------------------------------------------------------------- .../main/java/org/apache/ignite/IgniteDataStreamer.java | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/ignite/blob/285644ae/modules/core/src/main/java/org/apache/ignite/IgniteDataStreamer.java ---------------------------------------------------------------------- diff --git a/modules/core/src/main/java/org/apache/ignite/IgniteDataStreamer.java b/modules/core/src/main/java/org/apache/ignite/IgniteDataStreamer.java index 6665f59..e2473dc 100644 --- a/modules/core/src/main/java/org/apache/ignite/IgniteDataStreamer.java +++ b/modules/core/src/main/java/org/apache/ignite/IgniteDataStreamer.java @@ -31,8 +31,15 @@ import org.jetbrains.annotations.Nullable; * to make sure that there is the least amount of data movement possible and optimal * network and memory utilization. * <p> - * Note that data streamer is not transactional and therefore dishonours any active transaction - * when updating data. + * Note that data streamer data manipulation methods do not support transactions. + * When updating data with {@link #allowOverwrite()} set to {@code false} new entry + * is created on primary and backups if it has not existed. If {@link #allowOverwrite()} + * is {@code true} then batches are applied with regular {@code cache.put(..)} methods + * starting implicit transactions if streamer is targeted to a transactional cache. + * <p> + * However, explicit transactional updates inside are possible with custom {@link StreamReceiver}. + * This way batches can be applied within transaction(s) on target node. + * See {@link #receiver(StreamReceiver)} for details. * <p> * Note that streamer will stream data concurrently by multiple internal threads, so the * data may get to remote nodes in different order from which it was added to
