Thanks, Dmitry. I agree ultimately, DS API uniformity is a weighty reason. 2018-03-17 3:54 GMT+03:00 Dmitriy Setrakyan <dsetrak...@apache.org>:
> On Fri, Mar 16, 2018 at 7:39 AM, Andrey Kuznetsov <stku...@gmail.com> > wrote: > > > Dmitry, your way allows to reuse existing {{Ignite.set()}} API to create > > both set flavors. We can adopt it unless somebody in the community > objects. > > Personally, I like {{IgniteCache.asSet()}} approach proposed by Vladimir > O. > > more, since it emphasizes the difference between sets being created, but > > this will require API extension. > > > > Andrey, I am suggesting that Ignite.set(...) in non-collocated mode behaves > exactly the same as the proposed IgniteCache.asSet() method. I do not like > the IgniteCache.asSet() API because it is inconsistent with Ignite data > structure design. All data structures are provided on Ignite API directly > and we should not change that. > > D. > -- Best regards, Andrey Kuznetsov.