Home Verkennen Help
Registreren Inloggen
jiankun
/
GY_zhishiku
1
0
Vork 0
Bestanden Issues 0 Pull-aanvragen 0 Wiki
Boom: adec5c6d59
Aftakkingen Labels
GY_zhishiku
/
neo4jApi
/
app
/
vendor
/
elastic
/
transport
/
CHANGELOG.md

CHANGELOG.md 2.6 KB
Geschiedenis Ruwe

Changelog

8.3.0 (2022-06-27)

  • Release created to be compatible with 8.3 Elastic clients

8.2.0 (2022-06-22)

  • Release created to be compatible with 8.2 Elastic clients

8.1.0 (2022-04-12)

  • Release created to be compatible with 8.1 Elastic clients

8.0.1 (2022-03-30)

  • Support of psr/log v1, 2 and 3 to fix the dependency with elasticsearch/elasticsearch. a413687

8.0.0 (2022-03-24)

Finally, the 8.0.0 GA.

8.0.0-RC4 (2022-03-08)

Added the TransportException to extends the Throwableinterface.

8.0.0-RC3 (2022-02-26)

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.

8.0.0-RC2 (2022-02-23)

This RC2 release uses httplug v2.3.0 to provide a full retry async mechanism thanks to PR https://github.com/php-http/httplug/pull/168.

8.0.0-RC1 (2022-02-17)

This is the first release candidate for 8.0.0 containing some new features and changes compared with the previous 7.x Elastic transport.

Changes

  • the ConnectionPool namespace has been renamed in NodePool, consequently all the Connection classes has been renamed in Node
  • the previous Apache 2.0 LICENSE has been changed in MIT

New features

  • 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) and Transport::getAsyncClient() functions. If the PSR-18 client already implements the HttpAsyncClient interface you don't need to use the setAsyncClient() 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 a NoNodeAvailableException

7.14.0 (2021-08-03)

Release created to be compatible with 7.14 Elastic clients

7.13.0 (2021-05-25)

Release created to be compatible with 7.13 Elastic clients