TypeDB Client Java 2.14.3

Documentation: http://docs.vaticle.com/docs/client-api/java

Distribution

Available through https://repo.vaticle.com

<repositories>
    <repository>
        <id>repo.vaticle.com</id>
        <url>https://repo.vaticle.com/repository/maven/</url>
    </repository>
</repositories>
<dependencies>
    <dependency>
        <groupid>com.vaticle.typedb</groupid>
        <artifactid>typedb-client</artifactid>
        <version>2.14.3</version>
    </dependency>
</dependencies>

New Features

Bugs Fixed

Code Refactors

• Use latest typedb artifact

  We updated the typedb artifact to the latest released version 2.14.3.

Other Improvements

• Update VERSION to 2.14.3

• Implement cluster-capable schema retrieval

• Add transitive dependency on netty-handler to the connection package

  In line with bumping our netty dependencies (vaticle/dependencies#415), we need to include a transitive dependency that has been introduced on netty's side between the version we used to depend on and the version we now depend on.

TypeDB Client Java 2.14.2

Documentation: http://docs.vaticle.com/docs/client-api/java

Distribution

Available through https://repo.vaticle.com

<repositories>
    <repository>
        <id>repo.vaticle.com</id>
        <url>https://repo.vaticle.com/repository/maven/</url>
    </repository>
</repositories>
<dependencies>
    <dependency>
        <groupid>com.vaticle.typedb</groupid>
        <artifactid>typedb-client</artifactid>
        <version>2.14.2</version>
    </dependency>
</dependencies>

New Features

Bugs Fixed

Code Refactors

Other Improvements

• Bump behaviour repo

• bump VERSION to 2.14.2

• Update TypeQL to 2.14.0

TypeDB Client Java 2.14.0

Documentation: http://docs.vaticle.com/docs/client-api/java

Distribution

Available through https://repo.vaticle.com

<repositories>
    <repository>
        <id>repo.vaticle.com</id>
        <url>https://repo.vaticle.com/repository/maven/</url>
    </repository>
</repositories>
<dependencies>
    <dependency>
        <groupid>com.vaticle.typedb</groupid>
        <artifactid>typedb-client</artifactid>
        <version>2.14.0</version>
    </dependency>
</dependencies>

New Features

Bugs Fixed

Code Refactors

Other Improvements

• Update TypeQL to 2.14.0

• Bump VERSION to 2.14.0

• Improve getSchemaExceptions() to return TypeDBException that contains code and message

• Bump @vaticle_typedb_artifact

• Add GetSchemaExceptions to ConceptManager API

TypeDB Client Java 2.12.0

Documentation: http://docs.vaticle.com/docs/client-api/java

Distribution

Available through https://repo.vaticle.com

<repositories>
    <repository>
        <id>repo.vaticle.com</id>
        <url>https://repo.vaticle.com/repository/maven/</url>
    </repository>
</repositories>
<dependencies>
    <dependency>
        <groupid>com.vaticle.typedb</groupid>
        <artifactid>typedb-client</artifactid>
        <version>2.12.0</version>
    </dependency>
</dependencies>

New Features

Bugs Fixed

• Serialise queries without pretty printing

  To avoid injecting unintended tab characters into user attributes containing new lines, we utilise TypeQL's new unformatted to string conversion for serialising queries to the server.

Code Refactors

• Clean up maven related statements in WORKSPACE

  Group maven related statements together and add maven to all imported maven artifact aliases in the WORKSPACE file for clarity.

Other Improvements

• Remove vaticle_typeql_lang hanging dependency

• Update VERSION to 2.12.0

• Bump factory-tracing to released version

• Fix for deploying to GitHub, bump dependencies

  We've fixed the job involving deploying to GitHub and bumped dependencies in preparation for a release.

• Migrate to Factory

  We've migrated our continuous integration for this repo to Vaticle Factory from Grabl.

• Refactored 'isAbstract' to be a local field in Type as opposed to remote method

• rename .grabl to .factory

• Bump @vaticle_typedb_artifact

• Bump @vaticle_typedb_artifact

• Remove * imports

• Bump @vaticle_typedb_artifact

• Bump @vaticle_typedb_artifact

• Add getPlayerTypesExplicit() to RoleType

• Bump @vaticle_typedb_artifact (temporarily)

• *Introduce RoleType.getRelationsInstances() and Explicit()

• Introduce RoleType.getPlayerInstances() and getPlayerInstancesExplicit(), and rename getPlayers() to getPlayerTypes()

• Bump @vaticle_typedb_protocol

• Bump @vaticle_typedb_common

• Fixed automation.yml to refer to the new typeql repo

• Fixed TypeDBTransaction.onClose() to take in multiple callbacks

• Extend license checkstyle tests and update licenses

  We introduce a test that ensures that the license text is correct.

TypeDB Client Java 2.11.1

Documentation: http://docs.vaticle.com/docs/client-api/java

Distribution

Available through https://repo.vaticle.com

<repositories>
    <repository>
        <id>repo.vaticle.com</id>
        <url>https://repo.vaticle.com/repository/maven/</url>
    </repository>
</repositories>
<dependencies>
    <dependency>
        <groupid>com.vaticle.typedb</groupid>
        <artifactid>typedb-client</artifactid>
        <version>2.11.1</version>
    </dependency>
</dependencies>

New Features

Bugs Fixed

• Fix memory leak in long-running sessions

  A long running session used to keep the reference to each closed transaction, continually growing in size. These references are inaccessible from outside the session object. The problem was compounded in the write transactions, when the caller did not collect the responses received after insert queries, which were held onto by the closed transaction objects.

  We now dispose of the closed transaction objects and free their memory.

• When streaming, assume network latency >=1ms

  When streaming (e.g. match queries), we now assume the network latency is >=1ms, and have the server compensate accordingly. This sharply improves performance (up to 3x) when fetching answers from a server hosted at localhost.

Code Refactors

• Update TypeDB Cluster runner

  We updated TypeDB Cluster runner usage according to the latest version of the API

Other Improvements

• Update dependencies and VERSION to 2.11.1

• When streaming, assume network latency >=1ms (#386)

• Revert "When streaming, assume network latency is >=1ms"

• When streaming, assume network latency is >=1ms

• Bump copyright year to 2022

  We update the copyright header year to 2022.

TypeDB Client Java 2.11.0

Documentation: http://docs.vaticle.com/docs/client-api/java

Distribution

Available through https://repo.vaticle.com

<repositories>
    <repository>
        <id>repo.vaticle.com</id>
        <url>https://repo.vaticle.com/repository/maven/</url>
    </repository>
</repositories>
<dependencies>
    <dependency>
        <groupid>com.vaticle.typedb</groupid>
        <artifactid>typedb-client</artifactid>
        <version>2.11.0</version>
    </dependency>
</dependencies>

New Features

Bugs Fixed

Code Refactors

Other Improvements

• Update VERSION and typeql-lang-java to 2.11.0

• Update @vaticle_dependencies

• Bump @vaticle_typeql_lang_java

TypeDB Client Java 2.10.0

Documentation: http://docs.vaticle.com/docs/client-api/java

Distribution

Available through https://repo.vaticle.com

<repositories>
    <repository>
        <id>repo.vaticle.com</id>
        <url>https://repo.vaticle.com/repository/maven/</url>
    </repository>
</repositories>
<dependencies>
    <dependency>
        <groupid>com.vaticle.typedb</groupid>
        <artifactid>typedb-client</artifactid>
        <version>2.10.0</version>
    </dependency>
</dependencies>

New Features

• Define BDD test steps for extended Type Concept API

We define the functions corresponding to the BDD test steps introduced for the extended Type Concept API.

Bugs Fixed

Code Refactors

Other Improvements

• bump VERSION to 2.10.0 and update protocol

• Bump @vaticle_typedb_protocol

• Update TypeDB Cluster artifact version to 2.9.0

• Refined variable name

• Add helper methods for RelationType

• Add getSyntax() method to ThingType API

TypeDB Client Java 2.9.0

Documentation: http://docs.vaticle.com/docs/client-api/java

Distribution

Available through https://repo.vaticle.com

<repositories>
    <repository>
        <id>repo.vaticle.com</id>
        <url>https://repo.vaticle.com/repository/maven/</url>
    </repository>
</repositories>
<dependencies>
    <dependency>
        <groupid>com.vaticle.typedb</groupid>
        <artifactid>typedb-client</artifactid>
        <version>2.9.0</version>
    </dependency>
</dependencies>

New Features

Bugs Fixed

• Fix broken test-deployment-maven

The test-deployment-maven CI job was broken and has since been fixed.

Code Refactors

Other Improvements

• Update VERSION to 2.9.0

• Dependencies use tagged releases

• Upgrade to latest typedb-behaviour

• Use latest TypeDB Core that uses latest protocol for tests

• Implement getRelatesExplicit() and getRelatesOverridden() for RelationType

• Upgrade @vaticle_type_protocol

• Add getPlaysOverridden() to ThingType

• Add getPlaysExplicit() to ThingType

• Implement getOwnersExplicit method for AttributeType

• Add new ThingType methods: getOwnsExplicit and getOwnsOverridden

• Revert "Add maven_coordinates to all Bazel packages"

• Add maven_coordinates to all Bazel packages

• Upgrade to Bazel 5

Make the repository use Bazel 5. Bazel 4 and below only work with the deprecated Python 2, which is no longer included in some operating systems such as the latest Mac OS X.

• Implement typeSchema() and ruleSchema() on Database API

• Add missing overriding method ThingType.getSubtypesExplicit()

• Implement Type.getSubtypesExplicit and ThingType.getInstancesExplicit across Concept API

• Ignore caught exception in TypeDBSessionImpl.pulse()

• Refine TypeDBSessionImpl.close() logic

• Close session completely when pulse fails

• Add onClose() method on TypeDBSession

• Check if onClose is null before calling it

• Add Transaction.onClose() method to public API

• Upgrade @vaticle_typeql_lang_java

• Implement toString for NumericImpl

TypeDB Client Java 2.8.0

Documentation: http://docs.vaticle.com/docs/client-api/java

Distribution

Available through https://repo.vaticle.com

<repositories>
    <repository>
        <id>repo.vaticle.com</id>
        <url>https://repo.vaticle.com/repository/maven/</url>
    </repository>
</repositories>
<dependencies>
    <dependency>
        <groupid>com.vaticle.typedb</groupid>
        <artifactid>typedb-client</artifactid>
        <version>2.8.0</version>
    </dependency>
</dependencies>

New Features

Bugs Fixed

• Cluster client throws if the cluster is completely down

Cluster client throws an exception only if the cluster is completely down, instead of if any one server is down.

Code Refactors

• Query iterator only throws exeption once

We revert previous changes from #368 and #364, which made query queues and iterators throw the same error idempotently if there was one. However, this goes counter to standard usages of iterators and queues, which are not meant to behave idempotently (each item is only returned once, and if they have an error they should no longer be used).

Other Improvements

• Bump VERSION to 2.8.0 and dependencies to latest

• @vaticle_typedb_common version updated

• TypeDB Cluster artifact updated

• Bazel Cache is disabled temporarily until SSL is fixed

• Bump @vaticle_dependencies

• Bump @vaticle_typeql_lang_java

• Bump @vaticle_typeql_lang_java

• Bump @typeql_lang_java

TypeDB Client Java 2.6.2

Documentation: http://docs.vaticle.com/docs/client-api/java

Distribution

Available through https://repo.vaticle.com

<repositories>
    <repository>
        <id>repo.vaticle.com</id>
        <url>https://repo.vaticle.com/repository/maven/</url>
    </repository>
</repositories>
<dependencies>
    <dependency>
        <groupid>com.vaticle.typedb</groupid>
        <artifactid>typedb-client</artifactid>
        <version>2.6.2</version>
    </dependency>
</dependencies>

New Features

Bugs Fixed

• Don't delete response collectors in a transaction

We no longer delete response collectors in a transaction after receiving a response to a "single" request, or receiving a "DONE" message in a stream. This fixes a possible error when loading 50+ answers in one query and then performing a second query.

Code Refactors

• Store error on transaction stream

We store any exceptions received against the transaction stream (as well as query streams) in order to propagate the error to any future transaction operations, not just open query streams.

Other Improvements