You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the scope of MVP we should emulate batching. When tarantool will support this natively, we'll update the connector to support both cases depending of a protocol version.
The right way to implement this is to use pipelining: just send requests asynchronously and use sync (request id) to dispatch responses. In case of memtx storage engine the requests will be executed in the order of sending. There is no such guarantee in case of vinyl, but maybe we should just mention this as the implementation limitation for now.
It seems we should provide a way to 'upgrade' TarantoolConnection to TarantoolClientImpl to use asynchronous operations and reuse an open socket.
Activity
Totktonada commentedon Apr 12, 2019
In the scope of MVP we should emulate batching. When tarantool will support this natively, we'll update the connector to support both cases depending of a protocol version.
Totktonada commentedon Apr 12, 2019
After talk with @kostja on that:
The right way to implement this is to use pipelining: just send requests asynchronously and use
sync(request id) to dispatch responses. In case of memtx storage engine the requests will be executed in the order of sending. There is no such guarantee in case of vinyl, but maybe we should just mention this as the implementation limitation for now.It seems we should provide a way to 'upgrade' TarantoolConnection to TarantoolClientImpl to use asynchronous operations and reuse an open socket.
JDBC batch updates
JDBC batch updates
JDBC batch updates
JDBC batch updates
JDBC batch updates
JDBC batch updates