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
When using NEST 5.x clients, ProfiledElasticClient constructor throws the exception:
ProfiledElasticClient
System.MissingMethodException: 'Method not found: 'Void Nest.ElasticClient..ctor(Nest.IConnectionSettingsValues, Elasticsearch.Net.Connection.IConnection, Nest.INestSerializer, Elasticsearch.Net.Connection.ITransport)'.' at StackExchange.Profiling.Elasticsearch.ProfiledElasticClient..ctor(ConnectionSettings configuration)
Because it's a runtime exception, it can lead to bugs which can be discovered very late in the development process.
Suggestion: Put a version block in NuGet manifest that prevents it from being installed on NEST 5.x projects until the actual issue is addressed.
The text was updated successfully, but these errors were encountered:
Hi, @ssg, thanks for the report and provided suggestion!
Unfortunately, I don't currently use this plugin myself anymore, but willing to resolve any existing issues.
Going to apply required changes to support NEST 1.x, 2.x and 5.x, and maybe brand new MiniProfiler v4.
Expect update soon.
Sorry, something went wrong.
f08ce1d
@ssg, I've made required changes to support NEST 1.x, 2.x and 5.x. To keep SemVer compatibility, several packages were pushed to NuGet.
So, MiniProfiler.Elasticsearch dependencies are following now:
Great news (and so quick too), thanks!
No branches or pull requests
When using NEST 5.x clients,
ProfiledElasticClient
constructor throws the exception:Because it's a runtime exception, it can lead to bugs which can be discovered very late in the development process.
Suggestion: Put a version block in NuGet manifest that prevents it from being installed on NEST 5.x projects until the actual issue is addressed.
The text was updated successfully, but these errors were encountered: