datasift-java-3.2.14

Upgrades HTTP client which now creates a custom thread pool so that all threads Netty created are daemons.
This enables the client to shutdown when all non-daemon threads do.

The HTTP client uses a single thread pool for all request, the pool previously wouldn't kill its threads unless it was explicitly told to do so. There is a client.shutdown() method.

This behaviour was found to be confusing by customers so has changed as a result - The client will continue to use a single thread pool for all requests but the threads in the pool are now all daemons, this means that if the main thread and all other non-daemon threads exit, the thread pool will automatically shutdown without the user needing to explicitly do anything.

This new behaviour will see the JVM exit in an example like.

    public static void main(String... args) throws Exception {
        DataSiftConfig config = new DataSiftConfig("<USERNAME>", "<API_KEY>");
        final DataSiftClient datasift = new DataSiftClient(config);
            Stream result = datasift.compile("interaction.sample < 1").sync();
            if (result.isSuccessful()) {
                System.out.println("success " + result);
            } else {
                System.out.println("fail");
            }
    }

3.2.9

Added

Adds dependency convergence. Ensures only a single version of a library gets pulled in by the client and its dependencies

3.2.8

Added

• Support for the /account/usage API endpoint
• Support for the /pylon/sample API endpoint. Full details about the feature can be found in our platform release notes

3.2.1

datasift-java-3.2.1

[maven-release-plugin]  copy for tag datasift-java-3.2.1

3.1.0

Includes better connection management for streams.
Now sharding subscriptions over multiple websocket connections as and when needed.
Includes various bug fixes related to streaming and auto-reconnect.

datasift-java-beta3

capture interupt exception

datasift-java-beta2

clean up to meet style guide