We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The InMemoryTransportClient was renamed to InMemoryRequestInvoker in this pull request: Attempt at renames. This name change occurred in the 0.4.18 release, which was included in the 8.12 stack version. Reference: https://github.com/elastic/elastic-transport-net/blob/0.4.18/benchmarks/Elastic.Transport.Benchmarks/TransportBenchmarks.cs#L18.
InMemoryTransportClient
The changes to elastic-transport-net should be documented in the release notes, as they affect users utilizing transport directly.
elastic-transport-net
This should be documented as a new Release notes v8.12.0 entry section on https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/release-notes.html
Release notes v8.12.0
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The
InMemoryTransportClientwas renamed to InMemoryRequestInvoker in this pull request: Attempt at renames. This name change occurred in the 0.4.18 release, which was included in the 8.12 stack version. Reference: https://github.com/elastic/elastic-transport-net/blob/0.4.18/benchmarks/Elastic.Transport.Benchmarks/TransportBenchmarks.cs#L18.The changes to
elastic-transport-netshould be documented in the release notes, as they affect users utilizing transport directly.This should be documented as a new
Release notes v8.12.0entry section on https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/release-notes.htmlThe text was updated successfully, but these errors were encountered: