We have added default serializers to the 4.2 series here:
hazelcast/hazelcast#17934

There is a problem with backward compatibility. If a user had CustomSerializer for optional in 4.1, in 4.2 there is no way to use their serializers, and Hazelcast will throw java.lang.IllegalArgumentException: [class java.util.Optional] serializer cannot be overridden

Users can basi

Bug description:

• E111: indentation is not a multiple of four
• E123: closing bracket does not match indentation of opening bracket's line
• E126: continuation line over-indented for hanging indent
• E128: continuation line under-indented for visual indent
• E201: whitespace after '('
• E202: whitespace before ')'
• E203: whitespace before ':'
• E225: missing whitespace around opera

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

Java configuration functions are mutable.

For example the following setClearAppliedFunctionsOnBoot function is mutable. This function and others should be immutable.

Map<String, Double, PureFunction<String, Double, Apply.Map<Double>>> products =
  PersistentMap
    .functionsOn(Paths.get("my_dir"), stringSerializer(), doubleSerializer(), Arrays.asList(discount))
    .setClear

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.

We currently don't lint source code of tests which is not nice. The configuration should be placed in the ./test subdir and lint script should be updated in package.json.