Releases: typedb/typedb-common
TypeDB Common 2.24.0
New Features
Bugs Fixed
Code Refactors
-
Use localhost instead of 127.0.0.1 as server address in runner
We change the default host from 127.0.0.1 to localhost.
Other Improvements
- Update VERSION to 2.24.0
TypeDB Common 2.21.0
New Features
Bugs Fixed
Code Refactors
-
Update TypeDB Runner log output flag
As of typedb/typedb#6864, TypeDB has changed the name of the configuration argument to set the log file directory from
directory
tobase-dir
Other Improvements
-
Update VERSION to 2.21.0
-
Update bazel to 6.2.0 and use latest @vaticle_dependencies
TypeDB Common 2.19.0
New Features
Bugs Fixed
Code Refactors
- Update typedb startup scripts to reflect simplified dependencies folder
Updates typedb startup scripts (typedb
andtypedb.bat
) to reflect the simplified directory structure of server/lib introduced in typedb#6821
Other Improvements
- Update VERSION to 2.19.0
TypeDB Common 2.18.0
New Features
-
New class for approximate doubles comparison
Double
values should be compared approximately. We added a classDouble
with a methodequalsApproximate
for such comparison.
Bugs Fixed
Code Refactors
Other Improvements
-
Update VERSION to 2.18.0
-
Update release notes tool
We update dependencies so that we use the latest version of the release notes creation tool.
-
Generalise concat helpers
-
Fix console runner test
-
Rename collection method
TypeDB Common 2.17.0
New Features
-
Allow resetting and deleting the files of TypeDB Runners
We've enabled resetting and deleting the associated files for any TypeDBRunner. Resetting the Runner allows the saving of space by only deleting the state, rather than having to create a new runner.
We've also changed the Java language level to 11 for this project via Bazel.
Bugs Fixed
-
Fix TypeDB Windows Launcher UX
We can now launch TypeDB from any folder in Windows (provided TypeDB has been added to the user's environment).
TypeDB also gets launched in a new window, which the user can freely close or quit via Ctrl+C without interruption once they are finished.Fixes typedb/typedb#6780
Fixes typedb/typedb#6781
Code Refactors
-
Isolate runner environments
We prevent runners from ever using each others ports or file system state by always assigning random ports for the runners and always generating a new folder (via a random UUID) for the storage.
Other Improvements
-
Bump VERSION to 2.17.0
-
Add arrayContains method
-
Add containsAll(collection, ... values)
TypeDB Common 2.16.0
New Features
-
Cluster runner options
We've altered TypeDBClusterRunner, enabling us to pass in arguments that override the default configuration.
We've also fixed a bug that would prevent us from running 5 nodes in a cluster as 60000 + 5 * 1111 is 65555 which is greater than 65535, the maximum port number.
Bugs Fixed
Code Refactors
Other Improvements
-
Bump dependencies and VERSION to 2.16.0
-
Changed float to double in YAML parser
The float parsing in the YAML parser has been replaced with double parsing. This is because Java attempts to parse float-like YAML strings to double and throws an error when parsing them to float, and float parsing hadn't been used anywhere so it went unnoticed. Float-like strings are now parsed as doubles.
-
Refactor the 'runner' package to 'test'
- We've refactored the
//runner
package into//test
. We were too eager in our refactor that took us to this place, and failed to notice thatrules.bzl
in this package providedtypedb_java_test
andtypedb_kt_test
.
- We've refactored the
-
Update Kotlin dependencies in WORKSPACE
-
Bump @vaticle_dependencies
-
Deploy TypeDB Runner to Maven
We've added the deployment of our TypeDB Runner classes to our Maven repository so developers using build systems other than Bazel can make use of our runners.
-
Include TypeDB runners in common library jar
Currently, we don't include the test directory files in the main jar produced by typedb-common. As raised by a community member, we should include this so other people can make use of this via the provided jars.
TypeDB Common 2.12.0
New Features
Bugs Fixed
-
Fix runner archive extraction error
TypeDB Runner now handles unarchiving artifacts in a more rigorous way with respect to the provided indices. Now, we correctly check that a provided index is valid prior to an array lookup.
Code Refactors
-
Rename Grabl to Factory
We've changed all instances of Grabl to Factory in line with the change in name of our CI.
-
Refactor runner, adding support for kotlin
We extend TypeDB Runner to include support for tests run in Kotlin and refactor the way Runner finds passed archives for extraction and execution.
Other Improvements
-
Bump version of python installed by pyenv for github deployment
We've bumped the version of python installed by pyenv to resolve a segfault when building Python 3.6.10 on our current CI machines.
-
Re-instate use of pyenv
We've re-instated the use of pyenv in certain Factory job definitions. Removing it in favour of using the system python3 had far-reaching ramifications that proved too costly to immediately address.
-
Migrate to Factory
We've migrated our continuous integration for this repo to Vaticle Factory from Grabl.
-
bump VERSION to 2.12.0
-
Implement lazy permutations and intersection check
We impement lazy permutation generation and a short-circuiting intersection existence check.
-
Remove development branch
Eliminate the development branch which we do not require in this repository.
-
License checking
We introduce a test that ensures that the license text is correct.
TypeDB Common 2.11.1
New Features
Bugs Fixed
Code Refactors
-
Fully-featured TypeDB Cluster Runner
We have introduced a fully-featured TypeDB Cluster runner, capable of instantiating a cluster with multiple servers, accepting arbitrary configurations and providing programmatic APIs to manage the servers.
These capabilities grant a great deal of flexibility in testing various kinds of scenarios, such as different failure conditions, TLS configurations, and Logstash configurations.
This new runner is intended to replace the old, feature-limited runner, capable only of creating a single TypeDB Cluster server.
Other Improvements
-
Bump VERSION to 2.11.1
-
Update @vaticle_dependencies
-
Bump copyright year to 2022
We update the copyright header year to 2022.
-
Update @vaticle_dependencies
TypeDB Common 2.9.0
New Features
Bugs Fixed
Code Refactors
- TypeDB runner allocates unused ports
TypeDB runner will find an unused port to boot up with to guarantee a successful bootup. In the previous approach, a random integer was chosen which could sometimes happen to be a reserved or in-use port and would cause an error when booting the server.
Other Improvements
-
bump VERSION to 2.9.0
-
bump VERSION to 2.8.0
-
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.
TypeDB Common 2.7.0
New Features
- Make test runner support the latest TypeDB Cluster
The Cluster test runner supports the latest version of TypeDB Cluster.
Additionally, the runner can be configured more flexibly, allowing for any server parameters to be overridden.
Bugs Fixed
Code Refactors
Other Improvements
-
bump VERSION to 2.7.0
-
bump @Dependencies
-
Bazel Cache is disabled temporarily until SSL is fixed
-
Rename get() to content()
-
Expose Map and List content in YAML wrapper classes
-
Rename Yaml to YAML