[
https://issues.apache.org/jira/browse/IGNITE-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15106699#comment-15106699
]
Vladimir Ozerov commented on IGNITE-2285:
-----------------------------------------
There are several reasons to decline this change:
1) Ignite.Cache.DataStreamer() is longer than Ignite.DataStreamer(). This is
not true, that data streamer is usually used somewhere near cache. Data
streamer is usually used in some very special part of warmup code, while cache
is used for normal operations.
2) DataStreamer by default has little similar with Cache.put() because it goes
through completely different code path. User should not ask himself "should I
use put/putAll or streamer?". This is the main reason why streamer is put
outside cache.
3) ICache is already too complex and have too much methods.
4) This will be inconsistent with Java.
> .Net: Add ICache.GetDataStreamer
> --------------------------------
>
> Key: IGNITE-2285
> URL: https://issues.apache.org/jira/browse/IGNITE-2285
> Project: Ignite
> Issue Type: Improvement
> Components: interop
> Affects Versions: 1.1.4
> Reporter: Pavel Tupitsyn
> Assignee: Vladimir Ozerov
> Fix For: 1.6
>
>
> Currently we have IIgnite.GetDataStreamer, where user has to specify cache
> name and generic arguments.
> ICache.GetDataStreamer will infer both cache name and generic types for the
> user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
