Ganeshwara Hananda

Implement user role management API supporting the following functionalities: 1. Role CRUD 2. Assigning a role to a user

Client pulse

1

Heartbeat pulse should be managed at the client-level rather than session-level.

The pom.xml is incorrect in that it has two repositories: snapshot and release: https://github.com/graknlabs/client-java/blob/master/test/deployment/pom.xml ``` repo.grakn.ai.release repo.grakn.ai http://repo.grakn.ai/repository/maven/ repo.grakn.ai.snapshot repo.grakn.ai http://repo.grakn.ai/repository/maven-snapshot/ ``` This isn't good because it means we don't...

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...

## Problem to Solve A particular aspect of "cluster session" architecture is unintuitive: sessions aren't bound to a particular server, but rather to the whole cluster, with the ability to...

- The "internal" version of the command is used by the failover functionality and should be invokable from any replica. - The "user-facing" version is used for displaying replica status....

Implement user role management API supporting the following functionalities: 1. Role CRUD 2. Assigning a role to a user

The notion of performing read from secondary replicas in TypeDB Core does not make sense since there's only one server. However, the user can mistakenly do so since the API...

Client should not connect to an old primary replica

1

## Description Under network partitioning scenario, it is possible for a cluster to have two primary replicas. Primary replicas are assigned a term number, therefore it is possible to tell...