typedb-driver
typedb-driver copied to clipboard
typedb
TypeDB Drivers for Rust, Python, Java, Node.js, C, C++, and C#.
Currently, the client keeps track of various aspects of the replicas of a given database: role, term, and 'is prefered secondary' status. The information is stored in the [`ClusterDatabase`](https://github.com/vaticle/typedb-client-java/blob/master/connection/cluster/ClusterDatabase.java) class...
A new thread is created for each session. This can cause the machine to run out of threads. ## Steps to reproduce Open, and then immediately close, a session 10000...
## Problem to Solve When running concurrent queries in a transaction, and one of them fails causing the transaction to close, it's possible to get an unhelpful "Transaction closed" error...
## Problem to Solve Bulk-inserting data requires many network roundtrips. ## Proposed Solution We should introduce templated queries backed by client-to-server streamed data. Templated queries are also a standard feature...
## Problem to Solve Previously, we've had functions to clean the database via the Console. From the docs: > Cleaning a Database > > Cleaning the database, not to be...
## Problem to Solve Attribute has a generic type parameter, but AttributeType doesn't. This is inconsistent and a little odd. ## Proposed Solution We should either add the generic type...
## Problem to Solve The default logback loglevel is DEBUG, which causes large amounts of information from netty to be dumped into the launching terminal. ## Proposed Solution Change the...
## Problem to Solve Our Bazel workspace contains a private Grakn Cluster artifact for use when running Cluster tests, but it requires internal credentials, which community contributors don't have. ##...
## Problem to Solve `bazel build //...` fails without netrc credentials. This particularly impacts community contributors. ## Proposed Solution Setting `tags = ["manual"]` on every Cluster job should work. ##...
## Problem to Solve Currently, there's no easy way to check the health of Cluster server nodes. ## Current Workaround SSH into each machine individually, run `jps`, assuming that if...