- Allow installation of psr/http-message v2.0 #17
- Release created to be compatible with 8.5 Elastic clients
- Fixed the full body message in debug() log for Transport #11
- Release created to be compatible with 8.4 Elastic clients
- Added meta header info for Symfony HTTP client #9
- Added composer-runtime-api v2 for InstalledVersions #10
- Release created to be compatible with 8.3 Elastic clients
- Release created to be compatible with 8.2 Elastic clients
- Release created to be compatible with 8.1 Elastic clients
- Support of
psr/log
v1, 2 and 3 to fix the dependency withelasticsearch/elasticsearch
. a413687
Finally, the 8.0.0 GA.
Added the TransportException
to extends the Throwable
interface.
This RC3 release introduces the OnSuccessInterface
and OnFailureInterface
for manage the async code with the execution of a custom function during the
return of OnSuccess
and during the execution of OnFailure
. As default behaviour
the OnSuccessDefault
and OnFailureDefault
does not perform any operations.
This RC2 release uses httplug
v2.3.0 to provide a full retry async mechanism
thanks to PR php-http/httplug#168.
This is the first release candidate for 8.0.0 containing some new features and changes compared with the previous 7.x Elastic transport.
- the
ConnectionPool
namespace has been renamed inNodePool
, consequently all theConnection
classes has been renamed inNode
- the previous Apache 2.0 LICENSE has been changed in MIT
- added the usage of HTTPlug library to
autodiscovery PSR-18 client
and
HttpAsyncClient
interface using Promise. - added the
Trasnport::sendAsyncRequest(RequestInterface $request): Promise
to send a PSR-7 request using asynchronous request - added the
Transport::setAsyncClient(HttpAsyncClient $asyncClient)
andTransport::getAsyncClient()
functions. If the PSR-18 client already implements theHttpAsyncClient
interface you don't need to use thesetAsyncClient()
function, it will discovered automatically - added the
Transport::setRetries()
function to specify the number of HTTP request retries to apply. If the HTTP failures exceed the number of retries the client generates aNoNodeAvailableException
Release created to be compatible with 7.16 Elastic clients
Release created to be compatible with 7.15 Elastic clients
Release created to be compatible with 7.14 Elastic clients
Release created to be compatible with 7.13 Elastic clients