As far as I remember, it used to be public and then was moved to internal. The main issue with these updaters was that batching is dangerous because you can get deadlocks if keys are not sorted (which is the case for BATCHED). There is also BATCHED_SORTED, but it requires keys to be Comparable and I doubt we do any validation, so usability is questionable.
We can think about how to improve this functionality, but in current state I would definitely not include it on public API. User can always implement custom receiver if needed. -Val On Fri, Feb 16, 2018 at 5:04 AM, Denis Mekhanikov <dmekhani...@gmail.com> wrote: > Guys, > > I think, it makes sense to move this receiver implementation to public API. > It has much better performance, than the default one, that performs single > puts. > > I don't see any point in adding a batch size parameter to it though, since > DataStreamer already has such setting itself. > > Denis > > пт, 16 февр. 2018 г. в 13:29, Roman Guseinov <ro...@gromtech.ru>: > > > Val, > > > > I got what do you mean. Everything inside the org.apache.ignite.internal > is > > considered to be not public API. > > > > Best Regards, > > Roman > > > > > > > > -- > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > >
