in-memory

There is no technical difficulty to support includeValue option, looks like we are just missing it on the API level.

See SO question

In scope of #5970 Tarantool profile is introduced in lua-Harness suite. LuaJIT-related parts of the CI need to be adjusted for this profile usage.

Currently we don't have any mechanism to limit the maximum number of clients that could be handled simultaneously.

This feature should be designed properly. Here is some clue: https://redis.io/topics/clients#maximum-number-of-clients

There are no external core dependencies other than LZ4 and Snappy which are not used unless compression is configured. So they should be installable.

libraryDependencies += "io.swaydb" %% "lz4" % "version"
//OR 
libraryDependencies += "io.swaydb" %% "snappy" % "version"

For now we have to exclude

Use of the $geoNear pipeline stage results in:

[Error 40324] Unrecognized pipeline stage name: '$geoNear'

It's clear it is not currently supported in de.bwaldvogel.mongo.backend.aggregation.Aggregation.java

Example Mongo query usage:

db.places.aggregate([
   {
     $geoNear: {
        near: { type: "Point", coordinates: [ -73.99279 , 40.719296 ] },
        distance

Tracking issue

Go version: 1.17
Hazelcast Go Client version: 1.0.0
Hazelcast server version: 4.x
Number of the clients:
Cluster size, i.e. the number of Hazelcast cluster members:
OS version : Linux

Expected behaviour

logger.Config has method SetLogger that allows to set a custom logger matching Logger interface

Actual behaviour

logger.Config struct has no way to specify a custom logger im

Currently all the methods' API docstring are not up to date with behaviour. I saw some assertions that are for validation but their behaviour is not reflected in methods' api comments.