Eclipse Vert.x 3.9.0 released!

We are extremely pleased to announce that the Eclipse Vert.x version 3.9.0 has been released.

SQL Client fluent queries

The query API becomes fluent with the addition of a Query API for queries creation and configuration.

Collectors query now becomes part of the Query interface.

This is a breaking API change done under the tech preview status given that SQL client is a Vert.x 4 feature back-ported to Vert.x 3.

client.prepareQuery(sql).execute(tuple, ar -> ...);
 
// With a collector
client.preparedQuery(sql).collecting(Collectors.toList()).execute(tuple, ar -> ...);

You can read more about this new feature here.

Redis client backport

For Vert.x 4.0 we are doing a full reboot to the redis client. The functionality for the new client is ready to test on the master branch. In order to give users the opportunity to test and make the upcoming client even better it has been backported to the 3.9.0 release. The new client will allow users to connect to a single node, sentinel or cluster of redis nodes. The easiest way to start is:

Redis.createClient(
      vertx,
      new RedisOptions()
        .setConnectionString("redis://localhost:7006"))
      .send(Request.cmd(Command.PING), send -> {
        if (send.succeeded()) {
          // Should have received a pong...
        }
      });

Same-site cookies

SameSite Cookie policy has been added to the HTTP Server Cookies.

This is also applicable to web which allows cookie sessions to use SameSite cookies:

SessionHandler.create(store)
  .setCookieSameSite(CookieSameSite.STRICT);

Same-site cookies let servers require that a cookie shouldn’t be sent with cross-site (where Site is defined by the registrable domain) requests, which provides some protection against cross-site request forgery attacks (CSRF).

Kafka client upgrade

The Kafka client has been upgraded to Kafka 2.4.0 .

Our reactive client exposes the Kafka Admin API. As of 2.4.0 this API has been replaced by a new Kafka Admin API and therefore the Vert.x Kafka Admin API changes, e.g listing consumers groups

adminClient.listConsumerGroups(ar -> {
    System.out.println("ConsumerGroups= " + ar.result());
});

Future API

With the recent addition of Future#onComplete(...) supporting several handlers per Future in 3.9 made the Future#setHandler(...) method feel awkward. Indeed setHandler conveys the meaning that the Future manages a single handler. In 3.9 we deprecate Future#setHandler in favor of Future#onComplete.

EDNS disabled by default

EDNS is an extension mechanism for DNS (https://fr.wikipedia.org/wiki/EDNS) that should be disabled by default. It might cause unwanted issue and should be disabled by default.

Auth Deprecation warnings

As of 3.9.0 many APIs will be start warning about deprecations. There is a big refactoring and some breaking API changes coming on 4.0.0 and these warnings are just to give users a heads up that API will change on the upcoming version.

For more information about the upcoming 4.0 changes you can read 4.0.0-Deprecations-and-breaking-changes