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

box.cfg{}
s = box.schema.create_space('test')
_ = s:create_index('pk')
s:replace{1}
s:select({key = 'value'})

Result:

tarantool> s:select({key = 'value'})
---
- - [1]
...

Expected result: an error about invalid arguments. Otherwise on a huge table that might make tarantool process not responding for a long time and even die due to OOM.

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

RediSQL support multiple statements in the same "EXEC", hence it is possible and correct to do something like:

REDISQL.EXEC DB "INSERT INTO foo VALUES(1,2,3); INSERT INTO bar VALUES(2,3,4);" 

Which is quite convenient when mixed with BEGIN, COMMIT and ABORT instruction.

One problem is that all the statements are first prepared all together, and then executed, all together.

This

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

Currently, the Go client does not support Hazelcast's partition predicate.

Needed to check if code samples are runnable