TypeDB Console 3.0.0-alpha-4

Distribution

Download from TypeDB Package Repository: https://cloudsmith.io/~typedb/repos/public-release/packages/?q=name:^typedb-console+version:3.0.0-alpha-4

New Features

• Introduce TypeDB 3.0-alpha Console
  Reimagine TypeDB Console for the upcoming 3.0 release of TypeDB. This alpha version of the client lets you interact with the updated server, try out the new, even more elegant version of TypeQL, and get used to the new output format for data queries.
  Learn more about TypeDB 3.0 features here: https://typedb.com/blog/typedb-3-roadmap

Bugs Fixed

Code Refactors

Other Improvements

TypeDB Console 2.28.4

Distribution

Download from TypeDB Package Repository: https://cloudsmith.io/~typedb/repos/public-release/packages/?q=name:^typedb-console+version:2.28.4

New Features

Bugs Fixed

• Remove hard-coded value for transaction timeout
  Removes a hard-coded value for transaction timeout, which prevented the user's setting from taking effect.

Code Refactors

Other Improvements

• Bump dependencies for rules-python & pin CircleCI windows executor
  Bump dependencies for rules-python update. This fixes an error on windows builds in CircleCI.
  We also pin the image used for Windows builds on CircleCI to prevent updates from breaking the pipeline.

• Turn off statistics reporting in CI
  We turn off the statistics reporting in our CI builds not to send non-real diagnostics data.

TypeDB Console 2.28.2-rc1

Distribution

Download from TypeDB Package Repository: https://cloudsmith.io/~typedb/repos/public-release/packages/?q=name:^typedb-console+version:2.28.2-rc1

New Features

Bugs Fixed

Code Refactors

Other Improvements

• Turn off statistics reporting in CI
  We turn off the --diagnostics.reporting.statistics in our CI builds not to send non-real diagnostics data.

  In version 2.28 and earlier, this flag purely prevents TypeDB from sending any diagnostics data.
  In the upcoming version 2.28.1, this flag still allows TypeDB to send a single diagnostics snapshot with the information of when the diagnostics data has been turned off, but it happens only after the server runs for 1 hour, so we expect the CI builds not to reach this point and not to send any diagnostics data as well.

TypeDB Console 2.28.0

Distribution

Download from TypeDB Package Repository: https://cloudsmith.io/~typedb/repos/public-release/packages/?q=name:^typedb-console+version:2.28.0

New Features

• Cloud address translation

  We allow connection to the cloud servers using an address translation mapping (cf. typedb/typedb-driver#624). This is useful when the route from the user to the servers differs from the route the servers are configured with (e.g. connection to public-facing servers from an internal network).

  Example usage:

  console \
      --cloud=typedb1.domain.com:1729=typedb.local:11729,typedb2.domain.com:1729=typedb.local:21729 \
      --username=<user> --password=<password>

  or:

  console \
      --cloud=typedb1.domain.com:1729=typedb.local:11729 \
      --cloud=typedb2.domain.com:1729=typedb.local:21729 \
      --username=<user> --password=<password>

  Note: we currently require that the user provides translation for the addresses of all nodes in the Cloud deployment.

Bugs Fixed

Code Refactors

Other Improvements

• Fix git patch for Windows build

  We update the git patch used for workspace path shortening in Windows CI builds.

TypeDB Console 2.28.0-rc0

Distribution

Download from TypeDB Package Repository: https://cloudsmith.io/~typedb/repos/public-release/packages/?q=name:^typedb-console+version:2.28.0-rc0

New Features

• Cloud address translation

  We allow connection to the cloud servers using an address translation mapping (cf. typedb/typedb-driver#624). This is useful when the route from the user to the servers differs from the route the servers are configured with (e.g. connection to public-facing servers from an internal network).

  Example usage:

  console \
      --cloud=typedb1.domain.com:1729=typedb.local:11729,typedb2.domain.com:1729=typedb.local:21729 \
      --username=<user> --password=<password>

  or:

  console \
      --cloud=typedb1.domain.com:1729=typedb.local:11729 \
      --cloud=typedb2.domain.com:1729=typedb.local:21729 \
      --username=<user> --password=<password>

  Note: we currently require that the user provides translation for the addresses of all nodes in the Cloud deployment.

Bugs Fixed

Code Refactors

Other Improvements

• Merge master into development after 2.27.0 release

  We merge changes made during the release of 2.27.0 back into development.

TypeDB Console 2.27.0

Distribution

Download from TypeDB Package Repository: https://cloudsmith.io/~typedb/repos/public-release/packages/?q=name:^typedb-console+version:2.27.0

New Features

Bugs Fixed

Code Refactors

Other Improvements

• Fix null pointer in diagnostics user-id generation

TypeDB Console 2.27.0-rc0

Distribution

Download from TypeDB Package Repository: https://cloudsmith.io/~typedb/repos/public-release/packages/?q=name:^typedb-console+version:2.27.0-rc0

New Features

Bugs Fixed

Code Refactors

Other Improvements

• Fix null ptr in diagnostics user-id generation

TypeDB Console 2.26.6

Distribution

Download from TypeDB Package Repository: https://cloudsmith.io/~typedb/repos/public-release/packages/?q=name:^typedb-console+version:2.26.6

New Features

• Allow unicode TypeQL variables

  We update to the latest TypeQL, which supports unicode variables. This means TypeDB Console can now use unicode variables, as well as labels and string attribute values.

  For example, we can use Mandarin character sets:

  test::schema::write> define 人 sub entity;
                    
  Concepts have been defined
  
  test::schema::write*> commit
  Transaction changes committed
  > transaction test data write
  test::data::write> insert $人 isa 人; 
                  
  { $人 iid 0x826e80017fffffffffffffff isa 人; }
  
  answers: 1, total duration: 102 ms
  
  test::data::write*> commit
  Transaction changes committed
  > transaction test data read
  test::data::read> match $人 isa 人; get;
                 
  { $人 iid 0x826e80018000000000000000 isa 人; }
  
  answers: 1, total duration: 54 ms
  

Bugs Fixed

Code Refactors

• Use typedb-common from typeql/common, only deploy to CloudSmith

  We update Bazel dependencies and target paths following the merging of typedb-common into vaticle/typeql (see typedb/typeql#313).

  We also no longer upload build artifacts to the github releases page. Instead, the artifacts are available from our public cloudsmith repository, linked in the release notes.

• Bring in launch binary and console runner library from common

  We move the binary package and console-runner into this repository from typedb-common. typedb-console-runner is deployed to maven such that we can safely depend on it from other repos without creating Bazel dependency cycles.

Other Improvements

• Explicitly install python tool dependencies

  Since the upgrade to rules-python v0.24 (typedb/typedb-dependencies#460), we are required to explicitly install python dependencies in the WORKSPACE file. The python tools happened to be unused, so these errors were not visible until the sync dependencies tool was restored.

• Sync dependencies in CI

  We add a sync-dependencies job to be run in CI after successful snapshot and release deployments. The job sends a request to vaticle-bot to update all downstream dependencies.

  Note: this PR does not update the dependencies repo dependency. It will be updated automatically by the bot during its first pass.

• Only submit uncaught exceptions to diagnostics

• Set up CI filters for master-development workflow

• Make console runner use the same java installation as the calling process
  Makes TypeDB console runner use the same java installation as the calling process, so the system remain hermetic.

• Fix CI file and disable Core diagnostics in test

• Migrate artifact hosting to cloudsmith
  Updates artifact credentials, and deployment & consumption rules to use cloudsmith (repo.typedb.com) instead of the self-hosted sonatype repository (repo.vaticle.com).

• Remove typedb-console-runner's dependency on typedb-common

  We remove typedb-console-runner's dependency on common in order to reduce deployment complexity and make the maven library self-contained.

• Force hermitic JDK for builds

• Fix install-bazel-apt typo

TypeDB Console 2.26.6-rc1

Distribution

Download from TypeDB Package Repository: https://cloudsmith.io/~typedb/repos/public-release/packages/?q=name:^typedb-console+version:2.26.6-rc1

New Features

• Allow unicode TypeQL variables

  We update to the latest TypeQL, which supports unicode variables. This means TypeDB Console can now use unicode variables, as well as labels and string attribute values.

  For example, we can use Mandarin character sets:

  test::schema::write> define 人 sub entity;
                    
  Concepts have been defined
  
  test::schema::write*> commit
  Transaction changes committed
  > transaction test data write
  test::data::write> insert $人 isa 人; 
                  
  { $人 iid 0x826e80017fffffffffffffff isa 人; }
  
  answers: 1, total duration: 102 ms
  
  test::data::write*> commit
  Transaction changes committed
  > transaction test data read
  test::data::read> match $人 isa 人; get;
                 
  { $人 iid 0x826e80018000000000000000 isa 人; }
  
  answers: 1, total duration: 54 ms
  

Bugs Fixed

Code Refactors

• Use typedb-common from typeql/common, only deploy to CloudSmith

  We update Bazel dependencies and target paths following the merging of typedb-common into vaticle/typeql (see typedb/typeql#313).

  We also no longer upload build artifacts to the github releases page. Instead, the artifacts are available from our public cloudsmith repository, linked in the release notes.

• Bring in launch binary and console runner library from common

  We move the binary package and console-runner into this repository from typedb-common. typedb-console-runner is deployed to maven such that we can safely depend on it from other repos without creating Bazel dependency cycles.

Other Improvements

• Explicitly install python tool dependencies

  Since the upgrade to rules-python v0.24 (typedb/typedb-dependencies#460), we are required to explicitly install python dependencies in the WORKSPACE file. The python tools happened to be unused, so these errors were not visible until the sync dependencies tool was restored.

• Sync dependencies in CI

  We add a sync-dependencies job to be run in CI after successful snapshot and release deployments. The job sends a request to vaticle-bot to update all downstream dependencies.

  Note: this PR does not update the dependencies repo dependency. It will be updated automatically by the bot during its first pass.

• Only submit uncaught exceptions to diagnostics

• Set up CI filters for master-development workflow

• Make console runner use the same java installation as the calling process
  Makes TypeDB console runner use the same java installation as the calling process, so the system remain hermetic.

• Fix CI file and disable Core diagnostics in test

• Migrate artifact hosting to cloudsmith
  Updates artifact credentials, and deployment & consumption rules to use cloudsmith (repo.typedb.com) instead of the self-hosted sonatype repository (repo.vaticle.com).

• Remove typedb-console-runner's dependency on typedb-common

  We remove typedb-console-runner's dependency on common in order to reduce deployment complexity and make the maven library self-contained.

• Force hermitic JDK for builds

• Fix install-bazel-apt typo

TypeDB Console 2.26.5

New Features

Bugs Fixed

Code Refactors

• Reconfigure CircleCI executors to use GLIBC 2.26

  We compile and release TypeDB Console using an older version of Linux, which requires GLIBC 2.26 instead of GLIBC 2.27. This change switches the build platform to Amazon Linux 2 (via Docker), which is based on CentOS, instead of Ubuntu 18.04, which is based on Debian.

  Additionally, we upgrade the Windows Orb to 5.0.0, which also allowed using a larger executor to reduce CI time.

Other Improvements

• Shorten diagnostic ID to 16 hex chars