SphinxConnector.NET 5.1 has been released

by Dennis 1. February 2022 14:47

We're pleased to announce that SphinxConnector.NET 5.1 is now available via NuGet! You can also download a build from our site, but that only contains a version for .NET Framework 4.6.1. and higher.

This release adds a build for .NET 6.0, while .NET Core 2.1 has been removed as a target as it has gone out of support. We’ve added support for Manticore’s new LEVENSHTEIN() function and the DateOnly type introduced in .NET 6.

For a full list of changes, please refer to the version history.

Tags:

Announcements | SphinxConnector.NET

Updated Logging Packages available

by Dennis 19. February 2021 09:56

We’ve just uploaded new versions of all SphinxConnector.NET logging packages that contain a fix for a dependency issue. Due to an error in the build pipeline these packages were build while the version of SphinxConnector.NET was still at 4.4.0.

Tags:

SphinxConnector.NET

SphinxConnector.NET 5.0 has been released

by Dennis 9. February 2021 17:03

We're pleased to announce that SphinxConnector.NET 5.0 is now available via NuGet! You can also download a build from our site, but that only contains a version for .NET Framework 4.6.1. and higher.

With this release we’re saying good bye to Common.Logging, which has been replaced with our own logging abstraction. We’re providing separate NuGet packages for the most commonly used logging frameworks, namely:

Also included in SphinxConnector.NET is a simple console logging provider that can be used during development.

The second change in dependencies is the switch from JSON.NET to System.Text.Json as the default json handler. If for some reason you need to stay on JSON.NET, you can easily do so by implementing your own JsonObjectSerializer.

SphinxConnector.NET now includes builds for .NET Core 3.1 and .NET 5.0, where we’ve added implementations for new async methods to SphinxQLDataReader that were introduced with .NET Core 3.1. These builds also contain fluent API support for async enumerables via IFulltextQuery.ToAsyncEnumerable().

The biggest new feature is the introduction of prepared (sometimes also called ‘compiled’) queries to the fluent API.
The idea behind prepared queries is to create a query template that is parsed once and then reused on the following executions thus alleviating the overhead caused by parsing the expression tree and generating the SphinxQL statement. This can lead to significant reductions in allocations and time spend on parsing the expression tree of a query, especially in high load scenarios, while at the same time giving you all the advantages of a strongly typed query API. More about prepared queries can be found in the documentation.

For a full list of changes, please refer to the version history.

Tags:

Announcements | SphinxConnector.NET

SphinxConnector.NET 4.3 has been released

by Dennis 13. December 2019 16:00

We're pleased to announce that SphinxConnector.NET 4.3 is available for download and via NuGet!

In this release we've added a new BulkCopy class which efficiently copies data from an IDataReader to an index. We've also added support for the REMAP() function to the fluent API.

For a full list of changes, please refer to the version history.

Tags:

Announcements | SphinxConnector.NET

SphinxConnector.NET 4.2 has been released

by Administrator 30. May 2019 12:20

We're pleased to announce that SphinxConnector.NET 4.2 is available for download and via NuGet!

This release contains some compatibility fixes for Manticore 3 and adds support for Manticore's REGEX() and CONCAT() functions. If you are using JSON attributes in conjunction with the fluent API you might want to checkout two new methods we've added to the JsonObjectSerializer. You can use these methods to access the raw bytes or chars returned from searchd and pass them directly to your JSON serializer if supported. This avoids the creation of intermediate strings which can be a huge saving. If you're looking for alternatives to JSON.NET, which is used by default by SphinxConnector.NET: we recently did a comparison of JSON serializers which can be found here.

For a full list of changes, please refer to the version history.

Tags: