Dmitriy,
It's technically possible to produce both kinds of sets with
{{Ignite.set()}} call, but this will require to one more argument ('small'
vs 'large'). Doesn't it look less inuitive than separate
{{IgniteCache.asSet()}} ?
And of course, we don't want to leave existing implementation broken. Pavel
P. has prepared the fix as part of [1].
[1] https://issues.apache.org/jira/browse/IGNITE-5553
2018-03-15 5:40 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>:
> I am not sure I like the "asSet()" method. We already have Ignite.set(...)
> method and now introducing yet another one. The new design should fix the
> existing implementation. We cannot keep the broken implementation around
> and introduce yet another one. To be consistent, we should also stick to
> the IgniteSet abstraction.
>
> Just to be clear, I am in agreement that a non-collocated set should be
> based on a cache, but I do not see why the existing API cannot be re-used.
>
> D.
>
>
--
Best regards,
Andrey Kuznetsov.
